diff --git a/docs/es-ES/1.0.11/api-pages.html b/docs/es-ES/1.0.11/api-pages.html new file mode 100644 index 0000000000..35173f8a24 --- /dev/null +++ b/docs/es-ES/1.0.11/api-pages.html @@ -0,0 +1,175 @@ +Pages and Styles · Docusaurus

1.0.11

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>[Markdown syntax for a link](http://www.example.com)</MarkdownBlock>
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...         
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"  
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p><translate>I like translations</translate></p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">Community</translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require("../../server/translate.js").translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/api-pages/index.html b/docs/es-ES/1.0.11/api-pages/index.html new file mode 100644 index 0000000000..35173f8a24 --- /dev/null +++ b/docs/es-ES/1.0.11/api-pages/index.html @@ -0,0 +1,175 @@ +Pages and Styles · Docusaurus

1.0.11

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>[Markdown syntax for a link](http://www.example.com)</MarkdownBlock>
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...         
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"  
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p><translate>I like translations</translate></p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">Community</translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require("../../server/translate.js").translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/blog.html b/docs/es-ES/1.0.11/blog.html new file mode 100644 index 0000000000..320a1fcfb4 --- /dev/null +++ b/docs/es-ES/1.0.11/blog.html @@ -0,0 +1,129 @@ +Adding a Blog · Docusaurus

1.0.11

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipusm..
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The url associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook ID that is used to extract the profile picture.
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/blog/index.html b/docs/es-ES/1.0.11/blog/index.html new file mode 100644 index 0000000000..320a1fcfb4 --- /dev/null +++ b/docs/es-ES/1.0.11/blog/index.html @@ -0,0 +1,129 @@ +Adding a Blog · Docusaurus

1.0.11

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipusm..
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The url associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook ID that is used to extract the profile picture.
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/commands.html b/docs/es-ES/1.0.11/commands.html new file mode 100644 index 0000000000..0dc7115c22 --- /dev/null +++ b/docs/es-ES/1.0.11/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.11

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/commands/index.html b/docs/es-ES/1.0.11/commands/index.html new file mode 100644 index 0000000000..0dc7115c22 --- /dev/null +++ b/docs/es-ES/1.0.11/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.11

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/custom-pages.html b/docs/es-ES/1.0.11/custom-pages.html new file mode 100644 index 0000000000..656f9d0ded --- /dev/null +++ b/docs/es-ES/1.0.11/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.11

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/custom-pages/index.html b/docs/es-ES/1.0.11/custom-pages/index.html new file mode 100644 index 0000000000..656f9d0ded --- /dev/null +++ b/docs/es-ES/1.0.11/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.11

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/doc-markdown.html b/docs/es-ES/1.0.11/doc-markdown.html new file mode 100644 index 0000000000..d7762f7a0e --- /dev/null +++ b/docs/es-ES/1.0.11/doc-markdown.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.11

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/doc-markdown/index.html b/docs/es-ES/1.0.11/doc-markdown/index.html new file mode 100644 index 0000000000..d7762f7a0e --- /dev/null +++ b/docs/es-ES/1.0.11/doc-markdown/index.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.11

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/installation.html b/docs/es-ES/1.0.11/installation.html new file mode 100644 index 0000000000..2cbccfdd69 --- /dev/null +++ b/docs/es-ES/1.0.11/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.11

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Verificar la instalación

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/installation/index.html b/docs/es-ES/1.0.11/installation/index.html new file mode 100644 index 0000000000..2cbccfdd69 --- /dev/null +++ b/docs/es-ES/1.0.11/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.11

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Verificar la instalación

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/navigation.html b/docs/es-ES/1.0.11/navigation.html new file mode 100644 index 0000000000..87228852f2 --- /dev/null +++ b/docs/es-ES/1.0.11/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.11

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/navigation/index.html b/docs/es-ES/1.0.11/navigation/index.html new file mode 100644 index 0000000000..87228852f2 --- /dev/null +++ b/docs/es-ES/1.0.11/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.11

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/publishing.html b/docs/es-ES/1.0.11/publishing.html new file mode 100644 index 0000000000..97660f0c0e --- /dev/null +++ b/docs/es-ES/1.0.11/publishing.html @@ -0,0 +1,185 @@ +Publishing your site · Docusaurus

1.0.11

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's "html" directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+
    +
  • organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
    • +
  • projectName: The name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
    • +
+
+

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.

+

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:

+
    +
  • GIT_USER: The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
    • +
+

There are also two optional parameters that are set as environment variables:

+
    +

  • USE_SSH: If this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.

    • +

  • CURRENT_BRANCH: The branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.

    • +
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master   
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/publishing/index.html b/docs/es-ES/1.0.11/publishing/index.html new file mode 100644 index 0000000000..97660f0c0e --- /dev/null +++ b/docs/es-ES/1.0.11/publishing/index.html @@ -0,0 +1,185 @@ +Publishing your site · Docusaurus

1.0.11

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's "html" directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+
    +
  • organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
    • +
  • projectName: The name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
    • +
+
+

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.

+

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:

+
    +
  • GIT_USER: The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
    • +
+

There are also two optional parameters that are set as environment variables:

+
    +

  • USE_SSH: If this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.

    • +

  • CURRENT_BRANCH: The branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.

    • +
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master   
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/search.html b/docs/es-ES/1.0.11/search.html new file mode 100644 index 0000000000..9c0409a4e4 --- /dev/null +++ b/docs/es-ES/1.0.11/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.11

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/search/index.html b/docs/es-ES/1.0.11/search/index.html new file mode 100644 index 0000000000..9c0409a4e4 --- /dev/null +++ b/docs/es-ES/1.0.11/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.11

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/site-config.html b/docs/es-ES/1.0.11/site-config.html new file mode 100644 index 0000000000..6dfcf35564 --- /dev/null +++ b/docs/es-ES/1.0.11/site-config.html @@ -0,0 +1,231 @@ +siteConfig.js · Docusaurus

1.0.11

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - url for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - url for an Open Graph image. This image will show up when your site is shared on Facebook, Twitter and any other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - url for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with all fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+// For github.io type URLS, you would combine the url and baseUrl like:
+// url: "https://reasonml.github.io",
+// baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+// For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+// users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true"
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/site-config/index.html b/docs/es-ES/1.0.11/site-config/index.html new file mode 100644 index 0000000000..6dfcf35564 --- /dev/null +++ b/docs/es-ES/1.0.11/site-config/index.html @@ -0,0 +1,231 @@ +siteConfig.js · Docusaurus

1.0.11

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - url for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - url for an Open Graph image. This image will show up when your site is shared on Facebook, Twitter and any other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - url for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with all fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+// For github.io type URLS, you would combine the url and baseUrl like:
+// url: "https://reasonml.github.io",
+// baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+// For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+// users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true"
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/site-creation.html b/docs/es-ES/1.0.11/site-creation.html new file mode 100644 index 0000000000..4571d480f9 --- /dev/null +++ b/docs/es-ES/1.0.11/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.11

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/site-creation/index.html b/docs/es-ES/1.0.11/site-creation/index.html new file mode 100644 index 0000000000..4571d480f9 --- /dev/null +++ b/docs/es-ES/1.0.11/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.11

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/site-preparation.html b/docs/es-ES/1.0.11/site-preparation.html new file mode 100644 index 0000000000..501f69c375 --- /dev/null +++ b/docs/es-ES/1.0.11/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.11

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/site-preparation/index.html b/docs/es-ES/1.0.11/site-preparation/index.html new file mode 100644 index 0000000000..501f69c375 --- /dev/null +++ b/docs/es-ES/1.0.11/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.11

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/translation.html b/docs/es-ES/1.0.11/translation.html new file mode 100644 index 0000000000..8b5af37a26 --- /dev/null +++ b/docs/es-ES/1.0.11/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.11

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/translation/index.html b/docs/es-ES/1.0.11/translation/index.html new file mode 100644 index 0000000000..8b5af37a26 --- /dev/null +++ b/docs/es-ES/1.0.11/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.11

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/versioning.html b/docs/es-ES/1.0.11/versioning.html new file mode 100644 index 0000000000..63615532b5 --- /dev/null +++ b/docs/es-ES/1.0.11/versioning.html @@ -0,0 +1,108 @@ +Versioning · Docusaurus

1.0.11

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.11/versioning/index.html b/docs/es-ES/1.0.11/versioning/index.html new file mode 100644 index 0000000000..63615532b5 --- /dev/null +++ b/docs/es-ES/1.0.11/versioning/index.html @@ -0,0 +1,108 @@ +Versioning · Docusaurus

1.0.11

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/api-pages.html b/docs/es-ES/1.0.12/api-pages.html new file mode 100644 index 0000000000..058afb457f --- /dev/null +++ b/docs/es-ES/1.0.12/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.12

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/api-pages/index.html b/docs/es-ES/1.0.12/api-pages/index.html new file mode 100644 index 0000000000..058afb457f --- /dev/null +++ b/docs/es-ES/1.0.12/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.12

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/blog.html b/docs/es-ES/1.0.12/blog.html new file mode 100644 index 0000000000..4fe93648ec --- /dev/null +++ b/docs/es-ES/1.0.12/blog.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.12

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/blog/index.html b/docs/es-ES/1.0.12/blog/index.html new file mode 100644 index 0000000000..4fe93648ec --- /dev/null +++ b/docs/es-ES/1.0.12/blog/index.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.12

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/commands.html b/docs/es-ES/1.0.12/commands.html new file mode 100644 index 0000000000..e593cda282 --- /dev/null +++ b/docs/es-ES/1.0.12/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.12

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/commands/index.html b/docs/es-ES/1.0.12/commands/index.html new file mode 100644 index 0000000000..e593cda282 --- /dev/null +++ b/docs/es-ES/1.0.12/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.12

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/custom-pages.html b/docs/es-ES/1.0.12/custom-pages.html new file mode 100644 index 0000000000..4b453caa68 --- /dev/null +++ b/docs/es-ES/1.0.12/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.12

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/custom-pages/index.html b/docs/es-ES/1.0.12/custom-pages/index.html new file mode 100644 index 0000000000..4b453caa68 --- /dev/null +++ b/docs/es-ES/1.0.12/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.12

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/doc-markdown.html b/docs/es-ES/1.0.12/doc-markdown.html new file mode 100644 index 0000000000..ebd3526888 --- /dev/null +++ b/docs/es-ES/1.0.12/doc-markdown.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.12

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/doc-markdown/index.html b/docs/es-ES/1.0.12/doc-markdown/index.html new file mode 100644 index 0000000000..ebd3526888 --- /dev/null +++ b/docs/es-ES/1.0.12/doc-markdown/index.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.12

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/installation.html b/docs/es-ES/1.0.12/installation.html new file mode 100644 index 0000000000..00f3a56bae --- /dev/null +++ b/docs/es-ES/1.0.12/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.12

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Verificar la instalación

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/installation/index.html b/docs/es-ES/1.0.12/installation/index.html new file mode 100644 index 0000000000..00f3a56bae --- /dev/null +++ b/docs/es-ES/1.0.12/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.12

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Verificar la instalación

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/navigation.html b/docs/es-ES/1.0.12/navigation.html new file mode 100644 index 0000000000..6e0bef9552 --- /dev/null +++ b/docs/es-ES/1.0.12/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.12

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/navigation/index.html b/docs/es-ES/1.0.12/navigation/index.html new file mode 100644 index 0000000000..6e0bef9552 --- /dev/null +++ b/docs/es-ES/1.0.12/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.12

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/publishing.html b/docs/es-ES/1.0.12/publishing.html new file mode 100644 index 0000000000..a847518083 --- /dev/null +++ b/docs/es-ES/1.0.12/publishing.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.12

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/publishing/index.html b/docs/es-ES/1.0.12/publishing/index.html new file mode 100644 index 0000000000..a847518083 --- /dev/null +++ b/docs/es-ES/1.0.12/publishing/index.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.12

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/search.html b/docs/es-ES/1.0.12/search.html new file mode 100644 index 0000000000..ecedd05cdb --- /dev/null +++ b/docs/es-ES/1.0.12/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.12

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/search/index.html b/docs/es-ES/1.0.12/search/index.html new file mode 100644 index 0000000000..ecedd05cdb --- /dev/null +++ b/docs/es-ES/1.0.12/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.12

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/site-config.html b/docs/es-ES/1.0.12/site-config.html new file mode 100644 index 0000000000..a01cfe5bea --- /dev/null +++ b/docs/es-ES/1.0.12/site-config.html @@ -0,0 +1,234 @@ +siteConfig.js · Docusaurus

1.0.12

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/site-config/index.html b/docs/es-ES/1.0.12/site-config/index.html new file mode 100644 index 0000000000..a01cfe5bea --- /dev/null +++ b/docs/es-ES/1.0.12/site-config/index.html @@ -0,0 +1,234 @@ +siteConfig.js · Docusaurus

1.0.12

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/site-creation.html b/docs/es-ES/1.0.12/site-creation.html new file mode 100644 index 0000000000..17742de6ab --- /dev/null +++ b/docs/es-ES/1.0.12/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.12

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/site-creation/index.html b/docs/es-ES/1.0.12/site-creation/index.html new file mode 100644 index 0000000000..17742de6ab --- /dev/null +++ b/docs/es-ES/1.0.12/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.12

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/site-preparation.html b/docs/es-ES/1.0.12/site-preparation.html new file mode 100644 index 0000000000..4474f70bf1 --- /dev/null +++ b/docs/es-ES/1.0.12/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.12

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/site-preparation/index.html b/docs/es-ES/1.0.12/site-preparation/index.html new file mode 100644 index 0000000000..4474f70bf1 --- /dev/null +++ b/docs/es-ES/1.0.12/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.12

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/translation.html b/docs/es-ES/1.0.12/translation.html new file mode 100644 index 0000000000..a827f3cbe5 --- /dev/null +++ b/docs/es-ES/1.0.12/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.12

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/translation/index.html b/docs/es-ES/1.0.12/translation/index.html new file mode 100644 index 0000000000..a827f3cbe5 --- /dev/null +++ b/docs/es-ES/1.0.12/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.12

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/versioning.html b/docs/es-ES/1.0.12/versioning.html new file mode 100644 index 0000000000..9ce51fe344 --- /dev/null +++ b/docs/es-ES/1.0.12/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.12

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.12/versioning/index.html b/docs/es-ES/1.0.12/versioning/index.html new file mode 100644 index 0000000000..9ce51fe344 --- /dev/null +++ b/docs/es-ES/1.0.12/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.12

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/api-pages.html b/docs/es-ES/1.0.13/api-pages.html new file mode 100644 index 0000000000..6d0a91a5dc --- /dev/null +++ b/docs/es-ES/1.0.13/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.13

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/api-pages/index.html b/docs/es-ES/1.0.13/api-pages/index.html new file mode 100644 index 0000000000..6d0a91a5dc --- /dev/null +++ b/docs/es-ES/1.0.13/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.13

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/blog.html b/docs/es-ES/1.0.13/blog.html new file mode 100644 index 0000000000..bed67bc18d --- /dev/null +++ b/docs/es-ES/1.0.13/blog.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.13

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/blog/index.html b/docs/es-ES/1.0.13/blog/index.html new file mode 100644 index 0000000000..bed67bc18d --- /dev/null +++ b/docs/es-ES/1.0.13/blog/index.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.13

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/commands.html b/docs/es-ES/1.0.13/commands.html new file mode 100644 index 0000000000..666cc66fa1 --- /dev/null +++ b/docs/es-ES/1.0.13/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.13

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/commands/index.html b/docs/es-ES/1.0.13/commands/index.html new file mode 100644 index 0000000000..666cc66fa1 --- /dev/null +++ b/docs/es-ES/1.0.13/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.13

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/custom-pages.html b/docs/es-ES/1.0.13/custom-pages.html new file mode 100644 index 0000000000..66aa003fae --- /dev/null +++ b/docs/es-ES/1.0.13/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.13

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/custom-pages/index.html b/docs/es-ES/1.0.13/custom-pages/index.html new file mode 100644 index 0000000000..66aa003fae --- /dev/null +++ b/docs/es-ES/1.0.13/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.13

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/doc-markdown.html b/docs/es-ES/1.0.13/doc-markdown.html new file mode 100644 index 0000000000..89dd599f66 --- /dev/null +++ b/docs/es-ES/1.0.13/doc-markdown.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.13

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/doc-markdown/index.html b/docs/es-ES/1.0.13/doc-markdown/index.html new file mode 100644 index 0000000000..89dd599f66 --- /dev/null +++ b/docs/es-ES/1.0.13/doc-markdown/index.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.13

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/installation.html b/docs/es-ES/1.0.13/installation.html new file mode 100644 index 0000000000..505bc65362 --- /dev/null +++ b/docs/es-ES/1.0.13/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.13

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Verificar la instalación

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/installation/index.html b/docs/es-ES/1.0.13/installation/index.html new file mode 100644 index 0000000000..505bc65362 --- /dev/null +++ b/docs/es-ES/1.0.13/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.13

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Verificar la instalación

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/navigation.html b/docs/es-ES/1.0.13/navigation.html new file mode 100644 index 0000000000..1018f49716 --- /dev/null +++ b/docs/es-ES/1.0.13/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.13

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/navigation/index.html b/docs/es-ES/1.0.13/navigation/index.html new file mode 100644 index 0000000000..1018f49716 --- /dev/null +++ b/docs/es-ES/1.0.13/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.13

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/publishing.html b/docs/es-ES/1.0.13/publishing.html new file mode 100644 index 0000000000..214dcc1d43 --- /dev/null +++ b/docs/es-ES/1.0.13/publishing.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.13

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/publishing/index.html b/docs/es-ES/1.0.13/publishing/index.html new file mode 100644 index 0000000000..214dcc1d43 --- /dev/null +++ b/docs/es-ES/1.0.13/publishing/index.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.13

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/search.html b/docs/es-ES/1.0.13/search.html new file mode 100644 index 0000000000..7a83df137e --- /dev/null +++ b/docs/es-ES/1.0.13/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.13

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/search/index.html b/docs/es-ES/1.0.13/search/index.html new file mode 100644 index 0000000000..7a83df137e --- /dev/null +++ b/docs/es-ES/1.0.13/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.13

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/site-config.html b/docs/es-ES/1.0.13/site-config.html new file mode 100644 index 0000000000..d84b41adf4 --- /dev/null +++ b/docs/es-ES/1.0.13/site-config.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.13

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/site-config/index.html b/docs/es-ES/1.0.13/site-config/index.html new file mode 100644 index 0000000000..d84b41adf4 --- /dev/null +++ b/docs/es-ES/1.0.13/site-config/index.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.13

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/site-creation.html b/docs/es-ES/1.0.13/site-creation.html new file mode 100644 index 0000000000..0a856960fa --- /dev/null +++ b/docs/es-ES/1.0.13/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.13

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/site-creation/index.html b/docs/es-ES/1.0.13/site-creation/index.html new file mode 100644 index 0000000000..0a856960fa --- /dev/null +++ b/docs/es-ES/1.0.13/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.13

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/site-preparation.html b/docs/es-ES/1.0.13/site-preparation.html new file mode 100644 index 0000000000..3ac88ad529 --- /dev/null +++ b/docs/es-ES/1.0.13/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.13

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/site-preparation/index.html b/docs/es-ES/1.0.13/site-preparation/index.html new file mode 100644 index 0000000000..3ac88ad529 --- /dev/null +++ b/docs/es-ES/1.0.13/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.13

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/translation.html b/docs/es-ES/1.0.13/translation.html new file mode 100644 index 0000000000..ba684825b2 --- /dev/null +++ b/docs/es-ES/1.0.13/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.13

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/translation/index.html b/docs/es-ES/1.0.13/translation/index.html new file mode 100644 index 0000000000..ba684825b2 --- /dev/null +++ b/docs/es-ES/1.0.13/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.13

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/versioning.html b/docs/es-ES/1.0.13/versioning.html new file mode 100644 index 0000000000..75837211d7 --- /dev/null +++ b/docs/es-ES/1.0.13/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.13

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.13/versioning/index.html b/docs/es-ES/1.0.13/versioning/index.html new file mode 100644 index 0000000000..75837211d7 --- /dev/null +++ b/docs/es-ES/1.0.13/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.13

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/api-pages.html b/docs/es-ES/1.0.14/api-pages.html new file mode 100644 index 0000000000..eb5fb18aa2 --- /dev/null +++ b/docs/es-ES/1.0.14/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.14

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/api-pages/index.html b/docs/es-ES/1.0.14/api-pages/index.html new file mode 100644 index 0000000000..eb5fb18aa2 --- /dev/null +++ b/docs/es-ES/1.0.14/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.14

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

Urls for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/blog.html b/docs/es-ES/1.0.14/blog.html new file mode 100644 index 0000000000..af06c86135 --- /dev/null +++ b/docs/es-ES/1.0.14/blog.html @@ -0,0 +1,191 @@ +Adding a Blog · Docusaurus

1.0.14

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. +

    + Create a file index.html in website/static/. +

    +
    2. +
    <li>
+  <p>
+    Place the contents of the template below into <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Delete the dynamic landing page <code>website/pages/en/index.js</code>
+  </p>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+

+ 

<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=blog/">
+        <script type="text/javascript">
+            window.location.href = "blog/"
+        </script>
+        <title>Title of Your Blog</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='blog/'>link</a>.
+    </body>
+</html>
+

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/blog/index.html b/docs/es-ES/1.0.14/blog/index.html new file mode 100644 index 0000000000..af06c86135 --- /dev/null +++ b/docs/es-ES/1.0.14/blog/index.html @@ -0,0 +1,191 @@ +Adding a Blog · Docusaurus

1.0.14

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. +

    + Create a file index.html in website/static/. +

    +
    2. +
    <li>
+  <p>
+    Place the contents of the template below into <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Delete the dynamic landing page <code>website/pages/en/index.js</code>
+  </p>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+

+ 

<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=blog/">
+        <script type="text/javascript">
+            window.location.href = "blog/"
+        </script>
+        <title>Title of Your Blog</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='blog/'>link</a>.
+    </body>
+</html>
+

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/commands.html b/docs/es-ES/1.0.14/commands.html new file mode 100644 index 0000000000..4c52455074 --- /dev/null +++ b/docs/es-ES/1.0.14/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.14

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/commands/index.html b/docs/es-ES/1.0.14/commands/index.html new file mode 100644 index 0000000000..4c52455074 --- /dev/null +++ b/docs/es-ES/1.0.14/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.14

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/custom-pages.html b/docs/es-ES/1.0.14/custom-pages.html new file mode 100644 index 0000000000..8975a2d82a --- /dev/null +++ b/docs/es-ES/1.0.14/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.14

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/custom-pages/index.html b/docs/es-ES/1.0.14/custom-pages/index.html new file mode 100644 index 0000000000..8975a2d82a --- /dev/null +++ b/docs/es-ES/1.0.14/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.14

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/doc-markdown.html b/docs/es-ES/1.0.14/doc-markdown.html new file mode 100644 index 0000000000..8cc9147317 --- /dev/null +++ b/docs/es-ES/1.0.14/doc-markdown.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.14

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/doc-markdown/index.html b/docs/es-ES/1.0.14/doc-markdown/index.html new file mode 100644 index 0000000000..8cc9147317 --- /dev/null +++ b/docs/es-ES/1.0.14/doc-markdown/index.html @@ -0,0 +1,166 @@ +Markdown Features · Docusaurus

1.0.14

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/installation.html b/docs/es-ES/1.0.14/installation.html new file mode 100644 index 0000000000..ed45fdc658 --- /dev/null +++ b/docs/es-ES/1.0.14/installation.html @@ -0,0 +1,106 @@ +Installation · Docusaurus

1.0.14

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init > If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    4. +
+
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/installation/index.html b/docs/es-ES/1.0.14/installation/index.html new file mode 100644 index 0000000000..ed45fdc658 --- /dev/null +++ b/docs/es-ES/1.0.14/installation/index.html @@ -0,0 +1,106 @@ +Installation · Docusaurus

1.0.14

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init > If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    4. +
+
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/navigation.html b/docs/es-ES/1.0.14/navigation.html new file mode 100644 index 0000000000..095386c0bc --- /dev/null +++ b/docs/es-ES/1.0.14/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.14

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/navigation/index.html b/docs/es-ES/1.0.14/navigation/index.html new file mode 100644 index 0000000000..095386c0bc --- /dev/null +++ b/docs/es-ES/1.0.14/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.14

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/publishing.html b/docs/es-ES/1.0.14/publishing.html new file mode 100644 index 0000000000..d829734460 --- /dev/null +++ b/docs/es-ES/1.0.14/publishing.html @@ -0,0 +1,221 @@ +Publishing your site · Docusaurus

1.0.14

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +
  1. Select New site from Git
    2. +
  2. Connect to your preferred Git provider.
    3. +
  3. Select the branch to deploy. Default is master
    4. +
  4. Configure your build steps:
    5. +
+
    +
  • For your build command enter: cd website; npm install; npm run build;
    • +
  • For publish directory: build/<projectName> (use the projectName from your siteConfig)
    • +
+
    +
  1. Click Deploy site
    2. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/publishing/index.html b/docs/es-ES/1.0.14/publishing/index.html new file mode 100644 index 0000000000..d829734460 --- /dev/null +++ b/docs/es-ES/1.0.14/publishing/index.html @@ -0,0 +1,221 @@ +Publishing your site · Docusaurus

1.0.14

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +
  1. Select New site from Git
    2. +
  2. Connect to your preferred Git provider.
    3. +
  3. Select the branch to deploy. Default is master
    4. +
  4. Configure your build steps:
    5. +
+
    +
  • For your build command enter: cd website; npm install; npm run build;
    • +
  • For publish directory: build/<projectName> (use the projectName from your siteConfig)
    • +
+
    +
  1. Click Deploy site
    2. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/search.html b/docs/es-ES/1.0.14/search.html new file mode 100644 index 0000000000..a70fdf7a66 --- /dev/null +++ b/docs/es-ES/1.0.14/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.14

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/search/index.html b/docs/es-ES/1.0.14/search/index.html new file mode 100644 index 0000000000..a70fdf7a66 --- /dev/null +++ b/docs/es-ES/1.0.14/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.14

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Habilitando la barra de búsqueda

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/site-config.html b/docs/es-ES/1.0.14/site-config.html new file mode 100644 index 0000000000..02106386cc --- /dev/null +++ b/docs/es-ES/1.0.14/site-config.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.14

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/site-config/index.html b/docs/es-ES/1.0.14/site-config/index.html new file mode 100644 index 0000000000..02106386cc --- /dev/null +++ b/docs/es-ES/1.0.14/site-config/index.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.14

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/site-creation.html b/docs/es-ES/1.0.14/site-creation.html new file mode 100644 index 0000000000..b5136a44b2 --- /dev/null +++ b/docs/es-ES/1.0.14/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.14

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+        <script type="text/javascript">
+            window.location.href = "docs/id-of-doc-to-land-on.html"
+        </script>
+        <title>Your Site Title Here</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='docs/id-of-doc-to-land-on.html'>link</a>.
+    </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/site-creation/index.html b/docs/es-ES/1.0.14/site-creation/index.html new file mode 100644 index 0000000000..b5136a44b2 --- /dev/null +++ b/docs/es-ES/1.0.14/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.14

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+        <script type="text/javascript">
+            window.location.href = "docs/id-of-doc-to-land-on.html"
+        </script>
+        <title>Your Site Title Here</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='docs/id-of-doc-to-land-on.html'>link</a>.
+    </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/site-preparation.html b/docs/es-ES/1.0.14/site-preparation.html new file mode 100644 index 0000000000..db73aa4d7a --- /dev/null +++ b/docs/es-ES/1.0.14/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.14

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/site-preparation/index.html b/docs/es-ES/1.0.14/site-preparation/index.html new file mode 100644 index 0000000000..db73aa4d7a --- /dev/null +++ b/docs/es-ES/1.0.14/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.14

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/translation.html b/docs/es-ES/1.0.14/translation.html new file mode 100644 index 0000000000..7f5e6c4ea2 --- /dev/null +++ b/docs/es-ES/1.0.14/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.14

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/translation/index.html b/docs/es-ES/1.0.14/translation/index.html new file mode 100644 index 0000000000..7f5e6c4ea2 --- /dev/null +++ b/docs/es-ES/1.0.14/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.14

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/versioning.html b/docs/es-ES/1.0.14/versioning.html new file mode 100644 index 0000000000..46ff72c0fc --- /dev/null +++ b/docs/es-ES/1.0.14/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.14

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.14/versioning/index.html b/docs/es-ES/1.0.14/versioning/index.html new file mode 100644 index 0000000000..46ff72c0fc --- /dev/null +++ b/docs/es-ES/1.0.14/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.14

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/api-pages.html b/docs/es-ES/1.0.15/api-pages.html new file mode 100644 index 0000000000..d45e93dddf --- /dev/null +++ b/docs/es-ES/1.0.15/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.15

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/api-pages/index.html b/docs/es-ES/1.0.15/api-pages/index.html new file mode 100644 index 0000000000..d45e93dddf --- /dev/null +++ b/docs/es-ES/1.0.15/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.15

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/blog.html b/docs/es-ES/1.0.15/blog.html new file mode 100644 index 0000000000..67e5d2c645 --- /dev/null +++ b/docs/es-ES/1.0.15/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.0.15

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/blog/index.html b/docs/es-ES/1.0.15/blog/index.html new file mode 100644 index 0000000000..67e5d2c645 --- /dev/null +++ b/docs/es-ES/1.0.15/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.0.15

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/commands.html b/docs/es-ES/1.0.15/commands.html new file mode 100644 index 0000000000..840673c115 --- /dev/null +++ b/docs/es-ES/1.0.15/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.15

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/commands/index.html b/docs/es-ES/1.0.15/commands/index.html new file mode 100644 index 0000000000..840673c115 --- /dev/null +++ b/docs/es-ES/1.0.15/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.15

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Alias: examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/custom-pages.html b/docs/es-ES/1.0.15/custom-pages.html new file mode 100644 index 0000000000..3d64836433 --- /dev/null +++ b/docs/es-ES/1.0.15/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.15

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/custom-pages/index.html b/docs/es-ES/1.0.15/custom-pages/index.html new file mode 100644 index 0000000000..3d64836433 --- /dev/null +++ b/docs/es-ES/1.0.15/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.15

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/doc-markdown.html b/docs/es-ES/1.0.15/doc-markdown.html new file mode 100644 index 0000000000..2cc0cb3c45 --- /dev/null +++ b/docs/es-ES/1.0.15/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.15

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/doc-markdown/index.html b/docs/es-ES/1.0.15/doc-markdown/index.html new file mode 100644 index 0000000000..2cc0cb3c45 --- /dev/null +++ b/docs/es-ES/1.0.15/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.15

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/installation.html b/docs/es-ES/1.0.15/installation.html new file mode 100644 index 0000000000..ba76ddadc6 --- /dev/null +++ b/docs/es-ES/1.0.15/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.0.15

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/installation/index.html b/docs/es-ES/1.0.15/installation/index.html new file mode 100644 index 0000000000..ba76ddadc6 --- /dev/null +++ b/docs/es-ES/1.0.15/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.0.15

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/navigation.html b/docs/es-ES/1.0.15/navigation.html new file mode 100644 index 0000000000..99420a6aab --- /dev/null +++ b/docs/es-ES/1.0.15/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.0.15

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/navigation/index.html b/docs/es-ES/1.0.15/navigation/index.html new file mode 100644 index 0000000000..99420a6aab --- /dev/null +++ b/docs/es-ES/1.0.15/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.0.15

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/publishing.html b/docs/es-ES/1.0.15/publishing.html new file mode 100644 index 0000000000..965489f382 --- /dev/null +++ b/docs/es-ES/1.0.15/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.0.15

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/publishing/index.html b/docs/es-ES/1.0.15/publishing/index.html new file mode 100644 index 0000000000..965489f382 --- /dev/null +++ b/docs/es-ES/1.0.15/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.0.15

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/search.html b/docs/es-ES/1.0.15/search.html new file mode 100644 index 0000000000..e3d9c99cbd --- /dev/null +++ b/docs/es-ES/1.0.15/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.0.15

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/search/index.html b/docs/es-ES/1.0.15/search/index.html new file mode 100644 index 0000000000..e3d9c99cbd --- /dev/null +++ b/docs/es-ES/1.0.15/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.0.15

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/site-config.html b/docs/es-ES/1.0.15/site-config.html new file mode 100644 index 0000000000..5638c6484a --- /dev/null +++ b/docs/es-ES/1.0.15/site-config.html @@ -0,0 +1,239 @@ +siteConfig.js · Docusaurus

1.0.15

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site'
+
+
customDocsPath: 'website-docs'
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: 'doc1', label: 'Docs' },
+    { page: 'help', label: 'Help' },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B'
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink:
+    'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey:
+      '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github'
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ 'https://docusaurus.io/slash.js' ],
+  stylesheets: [ 'https://docusaurus.io/style.css' ],
+  facebookAppId: '1615782811974223',
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/site-config/index.html b/docs/es-ES/1.0.15/site-config/index.html new file mode 100644 index 0000000000..5638c6484a --- /dev/null +++ b/docs/es-ES/1.0.15/site-config/index.html @@ -0,0 +1,239 @@ +siteConfig.js · Docusaurus

1.0.15

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site'
+
+
customDocsPath: 'website-docs'
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: 'doc1', label: 'Docs' },
+    { page: 'help', label: 'Help' },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B'
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink:
+    'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey:
+      '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github'
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ 'https://docusaurus.io/slash.js' ],
+  stylesheets: [ 'https://docusaurus.io/style.css' ],
+  facebookAppId: '1615782811974223',
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/site-creation.html b/docs/es-ES/1.0.15/site-creation.html new file mode 100644 index 0000000000..0d9ca96093 --- /dev/null +++ b/docs/es-ES/1.0.15/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.15

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/site-creation/index.html b/docs/es-ES/1.0.15/site-creation/index.html new file mode 100644 index 0000000000..0d9ca96093 --- /dev/null +++ b/docs/es-ES/1.0.15/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.15

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/site-preparation.html b/docs/es-ES/1.0.15/site-preparation.html new file mode 100644 index 0000000000..dc97dab922 --- /dev/null +++ b/docs/es-ES/1.0.15/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.15

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/site-preparation/index.html b/docs/es-ES/1.0.15/site-preparation/index.html new file mode 100644 index 0000000000..dc97dab922 --- /dev/null +++ b/docs/es-ES/1.0.15/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.15

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/translation.html b/docs/es-ES/1.0.15/translation.html new file mode 100644 index 0000000000..d1f9b21828 --- /dev/null +++ b/docs/es-ES/1.0.15/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.0.15

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/translation/index.html b/docs/es-ES/1.0.15/translation/index.html new file mode 100644 index 0000000000..d1f9b21828 --- /dev/null +++ b/docs/es-ES/1.0.15/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.0.15

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/versioning.html b/docs/es-ES/1.0.15/versioning.html new file mode 100644 index 0000000000..1d307ef578 --- /dev/null +++ b/docs/es-ES/1.0.15/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.15

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.0.15/versioning/index.html b/docs/es-ES/1.0.15/versioning/index.html new file mode 100644 index 0000000000..1d307ef578 --- /dev/null +++ b/docs/es-ES/1.0.15/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.15

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/api-pages.html b/docs/es-ES/1.1.0/api-pages.html new file mode 100644 index 0000000000..a62ea6663f --- /dev/null +++ b/docs/es-ES/1.1.0/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.0

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/api-pages/index.html b/docs/es-ES/1.1.0/api-pages/index.html new file mode 100644 index 0000000000..a62ea6663f --- /dev/null +++ b/docs/es-ES/1.1.0/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.0

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/blog.html b/docs/es-ES/1.1.0/blog.html new file mode 100644 index 0000000000..9ffcb13edb --- /dev/null +++ b/docs/es-ES/1.1.0/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.0

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/blog/index.html b/docs/es-ES/1.1.0/blog/index.html new file mode 100644 index 0000000000..9ffcb13edb --- /dev/null +++ b/docs/es-ES/1.1.0/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.0

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/commands.html b/docs/es-ES/1.1.0/commands.html new file mode 100644 index 0000000000..7406cf3e55 --- /dev/null +++ b/docs/es-ES/1.1.0/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.0

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/commands/index.html b/docs/es-ES/1.1.0/commands/index.html new file mode 100644 index 0000000000..7406cf3e55 --- /dev/null +++ b/docs/es-ES/1.1.0/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.0

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/custom-pages.html b/docs/es-ES/1.1.0/custom-pages.html new file mode 100644 index 0000000000..562aadffb3 --- /dev/null +++ b/docs/es-ES/1.1.0/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/custom-pages/index.html b/docs/es-ES/1.1.0/custom-pages/index.html new file mode 100644 index 0000000000..562aadffb3 --- /dev/null +++ b/docs/es-ES/1.1.0/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/doc-markdown.html b/docs/es-ES/1.1.0/doc-markdown.html new file mode 100644 index 0000000000..c9fa686592 --- /dev/null +++ b/docs/es-ES/1.1.0/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.0

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/doc-markdown/index.html b/docs/es-ES/1.1.0/doc-markdown/index.html new file mode 100644 index 0000000000..c9fa686592 --- /dev/null +++ b/docs/es-ES/1.1.0/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.0

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/installation.html b/docs/es-ES/1.1.0/installation.html new file mode 100644 index 0000000000..461c6179ba --- /dev/null +++ b/docs/es-ES/1.1.0/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/installation/index.html b/docs/es-ES/1.1.0/installation/index.html new file mode 100644 index 0000000000..461c6179ba --- /dev/null +++ b/docs/es-ES/1.1.0/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/navigation.html b/docs/es-ES/1.1.0/navigation.html new file mode 100644 index 0000000000..c0e97bd33d --- /dev/null +++ b/docs/es-ES/1.1.0/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/navigation/index.html b/docs/es-ES/1.1.0/navigation/index.html new file mode 100644 index 0000000000..c0e97bd33d --- /dev/null +++ b/docs/es-ES/1.1.0/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/publishing.html b/docs/es-ES/1.1.0/publishing.html new file mode 100644 index 0000000000..67c7ed5feb --- /dev/null +++ b/docs/es-ES/1.1.0/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/publishing/index.html b/docs/es-ES/1.1.0/publishing/index.html new file mode 100644 index 0000000000..67c7ed5feb --- /dev/null +++ b/docs/es-ES/1.1.0/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/search.html b/docs/es-ES/1.1.0/search.html new file mode 100644 index 0000000000..89fe7b93ba --- /dev/null +++ b/docs/es-ES/1.1.0/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.0

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/search/index.html b/docs/es-ES/1.1.0/search/index.html new file mode 100644 index 0000000000..89fe7b93ba --- /dev/null +++ b/docs/es-ES/1.1.0/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.0

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/site-config.html b/docs/es-ES/1.1.0/site-config.html new file mode 100644 index 0000000000..9ab3ea5e1f --- /dev/null +++ b/docs/es-ES/1.1.0/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.0

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/site-config/index.html b/docs/es-ES/1.1.0/site-config/index.html new file mode 100644 index 0000000000..9ab3ea5e1f --- /dev/null +++ b/docs/es-ES/1.1.0/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.0

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/site-creation.html b/docs/es-ES/1.1.0/site-creation.html new file mode 100644 index 0000000000..f7fe755dc0 --- /dev/null +++ b/docs/es-ES/1.1.0/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/site-creation/index.html b/docs/es-ES/1.1.0/site-creation/index.html new file mode 100644 index 0000000000..f7fe755dc0 --- /dev/null +++ b/docs/es-ES/1.1.0/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/site-preparation.html b/docs/es-ES/1.1.0/site-preparation.html new file mode 100644 index 0000000000..a7fce1b15b --- /dev/null +++ b/docs/es-ES/1.1.0/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/site-preparation/index.html b/docs/es-ES/1.1.0/site-preparation/index.html new file mode 100644 index 0000000000..a7fce1b15b --- /dev/null +++ b/docs/es-ES/1.1.0/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/translation.html b/docs/es-ES/1.1.0/translation.html new file mode 100644 index 0000000000..a83cb03e26 --- /dev/null +++ b/docs/es-ES/1.1.0/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/translation/index.html b/docs/es-ES/1.1.0/translation/index.html new file mode 100644 index 0000000000..a83cb03e26 --- /dev/null +++ b/docs/es-ES/1.1.0/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/versioning.html b/docs/es-ES/1.1.0/versioning.html new file mode 100644 index 0000000000..ac1bbfe8ef --- /dev/null +++ b/docs/es-ES/1.1.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.0/versioning/index.html b/docs/es-ES/1.1.0/versioning/index.html new file mode 100644 index 0000000000..ac1bbfe8ef --- /dev/null +++ b/docs/es-ES/1.1.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/api-pages.html b/docs/es-ES/1.1.1/api-pages.html new file mode 100644 index 0000000000..36a160e4e4 --- /dev/null +++ b/docs/es-ES/1.1.1/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.1

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/api-pages/index.html b/docs/es-ES/1.1.1/api-pages/index.html new file mode 100644 index 0000000000..36a160e4e4 --- /dev/null +++ b/docs/es-ES/1.1.1/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.1

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/blog.html b/docs/es-ES/1.1.1/blog.html new file mode 100644 index 0000000000..84abb0a7b1 --- /dev/null +++ b/docs/es-ES/1.1.1/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.1

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/blog/index.html b/docs/es-ES/1.1.1/blog/index.html new file mode 100644 index 0000000000..84abb0a7b1 --- /dev/null +++ b/docs/es-ES/1.1.1/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.1

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/commands.html b/docs/es-ES/1.1.1/commands.html new file mode 100644 index 0000000000..b244dd31a6 --- /dev/null +++ b/docs/es-ES/1.1.1/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.1

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/commands/index.html b/docs/es-ES/1.1.1/commands/index.html new file mode 100644 index 0000000000..b244dd31a6 --- /dev/null +++ b/docs/es-ES/1.1.1/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.1

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/custom-pages.html b/docs/es-ES/1.1.1/custom-pages.html new file mode 100644 index 0000000000..23a5ab30bd --- /dev/null +++ b/docs/es-ES/1.1.1/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/custom-pages/index.html b/docs/es-ES/1.1.1/custom-pages/index.html new file mode 100644 index 0000000000..23a5ab30bd --- /dev/null +++ b/docs/es-ES/1.1.1/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/doc-markdown.html b/docs/es-ES/1.1.1/doc-markdown.html new file mode 100644 index 0000000000..2fbb2970d5 --- /dev/null +++ b/docs/es-ES/1.1.1/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.1

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/doc-markdown/index.html b/docs/es-ES/1.1.1/doc-markdown/index.html new file mode 100644 index 0000000000..2fbb2970d5 --- /dev/null +++ b/docs/es-ES/1.1.1/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.1

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/installation.html b/docs/es-ES/1.1.1/installation.html new file mode 100644 index 0000000000..5c4e7a2393 --- /dev/null +++ b/docs/es-ES/1.1.1/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/installation/index.html b/docs/es-ES/1.1.1/installation/index.html new file mode 100644 index 0000000000..5c4e7a2393 --- /dev/null +++ b/docs/es-ES/1.1.1/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/navigation.html b/docs/es-ES/1.1.1/navigation.html new file mode 100644 index 0000000000..17d4be785b --- /dev/null +++ b/docs/es-ES/1.1.1/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/navigation/index.html b/docs/es-ES/1.1.1/navigation/index.html new file mode 100644 index 0000000000..17d4be785b --- /dev/null +++ b/docs/es-ES/1.1.1/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/publishing.html b/docs/es-ES/1.1.1/publishing.html new file mode 100644 index 0000000000..948281a562 --- /dev/null +++ b/docs/es-ES/1.1.1/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/publishing/index.html b/docs/es-ES/1.1.1/publishing/index.html new file mode 100644 index 0000000000..948281a562 --- /dev/null +++ b/docs/es-ES/1.1.1/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/search.html b/docs/es-ES/1.1.1/search.html new file mode 100644 index 0000000000..785e90862c --- /dev/null +++ b/docs/es-ES/1.1.1/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.1

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/search/index.html b/docs/es-ES/1.1.1/search/index.html new file mode 100644 index 0000000000..785e90862c --- /dev/null +++ b/docs/es-ES/1.1.1/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.1

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/site-config.html b/docs/es-ES/1.1.1/site-config.html new file mode 100644 index 0000000000..da10f8e885 --- /dev/null +++ b/docs/es-ES/1.1.1/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.1

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/site-config/index.html b/docs/es-ES/1.1.1/site-config/index.html new file mode 100644 index 0000000000..da10f8e885 --- /dev/null +++ b/docs/es-ES/1.1.1/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.1

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/site-creation.html b/docs/es-ES/1.1.1/site-creation.html new file mode 100644 index 0000000000..586b2e50bf --- /dev/null +++ b/docs/es-ES/1.1.1/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/site-creation/index.html b/docs/es-ES/1.1.1/site-creation/index.html new file mode 100644 index 0000000000..586b2e50bf --- /dev/null +++ b/docs/es-ES/1.1.1/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/site-preparation.html b/docs/es-ES/1.1.1/site-preparation.html new file mode 100644 index 0000000000..7f687f8337 --- /dev/null +++ b/docs/es-ES/1.1.1/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/site-preparation/index.html b/docs/es-ES/1.1.1/site-preparation/index.html new file mode 100644 index 0000000000..7f687f8337 --- /dev/null +++ b/docs/es-ES/1.1.1/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/translation.html b/docs/es-ES/1.1.1/translation.html new file mode 100644 index 0000000000..dcdf57aa19 --- /dev/null +++ b/docs/es-ES/1.1.1/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/translation/index.html b/docs/es-ES/1.1.1/translation/index.html new file mode 100644 index 0000000000..dcdf57aa19 --- /dev/null +++ b/docs/es-ES/1.1.1/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/versioning.html b/docs/es-ES/1.1.1/versioning.html new file mode 100644 index 0000000000..1aa69239cb --- /dev/null +++ b/docs/es-ES/1.1.1/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.1/versioning/index.html b/docs/es-ES/1.1.1/versioning/index.html new file mode 100644 index 0000000000..1aa69239cb --- /dev/null +++ b/docs/es-ES/1.1.1/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/api-pages.html b/docs/es-ES/1.1.2/api-pages.html new file mode 100644 index 0000000000..768ce35dda --- /dev/null +++ b/docs/es-ES/1.1.2/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.2

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/api-pages/index.html b/docs/es-ES/1.1.2/api-pages/index.html new file mode 100644 index 0000000000..768ce35dda --- /dev/null +++ b/docs/es-ES/1.1.2/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.2

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/blog.html b/docs/es-ES/1.1.2/blog.html new file mode 100644 index 0000000000..2bc62cc202 --- /dev/null +++ b/docs/es-ES/1.1.2/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.2

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/blog/index.html b/docs/es-ES/1.1.2/blog/index.html new file mode 100644 index 0000000000..2bc62cc202 --- /dev/null +++ b/docs/es-ES/1.1.2/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.2

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/commands.html b/docs/es-ES/1.1.2/commands.html new file mode 100644 index 0000000000..fa9c473c91 --- /dev/null +++ b/docs/es-ES/1.1.2/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.2

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/commands/index.html b/docs/es-ES/1.1.2/commands/index.html new file mode 100644 index 0000000000..fa9c473c91 --- /dev/null +++ b/docs/es-ES/1.1.2/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.2

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/custom-pages.html b/docs/es-ES/1.1.2/custom-pages.html new file mode 100644 index 0000000000..6a335301ad --- /dev/null +++ b/docs/es-ES/1.1.2/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.2

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/custom-pages/index.html b/docs/es-ES/1.1.2/custom-pages/index.html new file mode 100644 index 0000000000..6a335301ad --- /dev/null +++ b/docs/es-ES/1.1.2/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.2

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/doc-markdown.html b/docs/es-ES/1.1.2/doc-markdown.html new file mode 100644 index 0000000000..179e1822ed --- /dev/null +++ b/docs/es-ES/1.1.2/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.2

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/doc-markdown/index.html b/docs/es-ES/1.1.2/doc-markdown/index.html new file mode 100644 index 0000000000..179e1822ed --- /dev/null +++ b/docs/es-ES/1.1.2/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.2

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/installation.html b/docs/es-ES/1.1.2/installation.html new file mode 100644 index 0000000000..26a08d28e2 --- /dev/null +++ b/docs/es-ES/1.1.2/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.2

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/installation/index.html b/docs/es-ES/1.1.2/installation/index.html new file mode 100644 index 0000000000..26a08d28e2 --- /dev/null +++ b/docs/es-ES/1.1.2/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.2

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/navigation.html b/docs/es-ES/1.1.2/navigation.html new file mode 100644 index 0000000000..435a15a0b2 --- /dev/null +++ b/docs/es-ES/1.1.2/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.2

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/navigation/index.html b/docs/es-ES/1.1.2/navigation/index.html new file mode 100644 index 0000000000..435a15a0b2 --- /dev/null +++ b/docs/es-ES/1.1.2/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.2

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/publishing.html b/docs/es-ES/1.1.2/publishing.html new file mode 100644 index 0000000000..82b3eb45bf --- /dev/null +++ b/docs/es-ES/1.1.2/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.2

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/publishing/index.html b/docs/es-ES/1.1.2/publishing/index.html new file mode 100644 index 0000000000..82b3eb45bf --- /dev/null +++ b/docs/es-ES/1.1.2/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.2

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/search.html b/docs/es-ES/1.1.2/search.html new file mode 100644 index 0000000000..afb7d0b436 --- /dev/null +++ b/docs/es-ES/1.1.2/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.2

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/search/index.html b/docs/es-ES/1.1.2/search/index.html new file mode 100644 index 0000000000..afb7d0b436 --- /dev/null +++ b/docs/es-ES/1.1.2/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.2

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/site-config.html b/docs/es-ES/1.1.2/site-config.html new file mode 100644 index 0000000000..4d5128f05a --- /dev/null +++ b/docs/es-ES/1.1.2/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.2

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/site-config/index.html b/docs/es-ES/1.1.2/site-config/index.html new file mode 100644 index 0000000000..4d5128f05a --- /dev/null +++ b/docs/es-ES/1.1.2/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.2

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/site-creation.html b/docs/es-ES/1.1.2/site-creation.html new file mode 100644 index 0000000000..a2f2dc29b1 --- /dev/null +++ b/docs/es-ES/1.1.2/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.2

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/site-creation/index.html b/docs/es-ES/1.1.2/site-creation/index.html new file mode 100644 index 0000000000..a2f2dc29b1 --- /dev/null +++ b/docs/es-ES/1.1.2/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.2

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/site-preparation.html b/docs/es-ES/1.1.2/site-preparation.html new file mode 100644 index 0000000000..ce45717993 --- /dev/null +++ b/docs/es-ES/1.1.2/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.2

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/site-preparation/index.html b/docs/es-ES/1.1.2/site-preparation/index.html new file mode 100644 index 0000000000..ce45717993 --- /dev/null +++ b/docs/es-ES/1.1.2/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.2

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/translation.html b/docs/es-ES/1.1.2/translation.html new file mode 100644 index 0000000000..b8cc7c657c --- /dev/null +++ b/docs/es-ES/1.1.2/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.2

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/translation/index.html b/docs/es-ES/1.1.2/translation/index.html new file mode 100644 index 0000000000..b8cc7c657c --- /dev/null +++ b/docs/es-ES/1.1.2/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.2

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/versioning.html b/docs/es-ES/1.1.2/versioning.html new file mode 100644 index 0000000000..5855526bd1 --- /dev/null +++ b/docs/es-ES/1.1.2/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.2

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.2/versioning/index.html b/docs/es-ES/1.1.2/versioning/index.html new file mode 100644 index 0000000000..5855526bd1 --- /dev/null +++ b/docs/es-ES/1.1.2/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.2

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/api-pages.html b/docs/es-ES/1.1.3/api-pages.html new file mode 100644 index 0000000000..949e4269e7 --- /dev/null +++ b/docs/es-ES/1.1.3/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.3

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/api-pages/index.html b/docs/es-ES/1.1.3/api-pages/index.html new file mode 100644 index 0000000000..949e4269e7 --- /dev/null +++ b/docs/es-ES/1.1.3/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.3

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/blog.html b/docs/es-ES/1.1.3/blog.html new file mode 100644 index 0000000000..7ba75d0776 --- /dev/null +++ b/docs/es-ES/1.1.3/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.3

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/blog/index.html b/docs/es-ES/1.1.3/blog/index.html new file mode 100644 index 0000000000..7ba75d0776 --- /dev/null +++ b/docs/es-ES/1.1.3/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.3

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/commands.html b/docs/es-ES/1.1.3/commands.html new file mode 100644 index 0000000000..6446dc5804 --- /dev/null +++ b/docs/es-ES/1.1.3/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.3

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/commands/index.html b/docs/es-ES/1.1.3/commands/index.html new file mode 100644 index 0000000000..6446dc5804 --- /dev/null +++ b/docs/es-ES/1.1.3/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.3

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/custom-pages.html b/docs/es-ES/1.1.3/custom-pages.html new file mode 100644 index 0000000000..b6d9582a71 --- /dev/null +++ b/docs/es-ES/1.1.3/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.3

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/custom-pages/index.html b/docs/es-ES/1.1.3/custom-pages/index.html new file mode 100644 index 0000000000..b6d9582a71 --- /dev/null +++ b/docs/es-ES/1.1.3/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.3

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/doc-markdown.html b/docs/es-ES/1.1.3/doc-markdown.html new file mode 100644 index 0000000000..177f789f8f --- /dev/null +++ b/docs/es-ES/1.1.3/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.3

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/doc-markdown/index.html b/docs/es-ES/1.1.3/doc-markdown/index.html new file mode 100644 index 0000000000..177f789f8f --- /dev/null +++ b/docs/es-ES/1.1.3/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.3

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/installation.html b/docs/es-ES/1.1.3/installation.html new file mode 100644 index 0000000000..a3850bb637 --- /dev/null +++ b/docs/es-ES/1.1.3/installation.html @@ -0,0 +1,112 @@ +Installation · Docusaurus

1.1.3

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   └── 2017-04-10-blog-post-two.md
+    ├── core
+    │   └── Footer.js
+    ├── node_modules
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/installation/index.html b/docs/es-ES/1.1.3/installation/index.html new file mode 100644 index 0000000000..a3850bb637 --- /dev/null +++ b/docs/es-ES/1.1.3/installation/index.html @@ -0,0 +1,112 @@ +Installation · Docusaurus

1.1.3

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   └── 2017-04-10-blog-post-two.md
+    ├── core
+    │   └── Footer.js
+    ├── node_modules
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/navigation.html b/docs/es-ES/1.1.3/navigation.html new file mode 100644 index 0000000000..5bc3bd5984 --- /dev/null +++ b/docs/es-ES/1.1.3/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.3

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/navigation/index.html b/docs/es-ES/1.1.3/navigation/index.html new file mode 100644 index 0000000000..5bc3bd5984 --- /dev/null +++ b/docs/es-ES/1.1.3/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.3

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/publishing.html b/docs/es-ES/1.1.3/publishing.html new file mode 100644 index 0000000000..cea24bb6c1 --- /dev/null +++ b/docs/es-ES/1.1.3/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.3

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/publishing/index.html b/docs/es-ES/1.1.3/publishing/index.html new file mode 100644 index 0000000000..cea24bb6c1 --- /dev/null +++ b/docs/es-ES/1.1.3/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.3

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/search.html b/docs/es-ES/1.1.3/search.html new file mode 100644 index 0000000000..9badb6b64c --- /dev/null +++ b/docs/es-ES/1.1.3/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.3

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/search/index.html b/docs/es-ES/1.1.3/search/index.html new file mode 100644 index 0000000000..9badb6b64c --- /dev/null +++ b/docs/es-ES/1.1.3/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.3

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/site-config.html b/docs/es-ES/1.1.3/site-config.html new file mode 100644 index 0000000000..4da63e37b6 --- /dev/null +++ b/docs/es-ES/1.1.3/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.3

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/site-config/index.html b/docs/es-ES/1.1.3/site-config/index.html new file mode 100644 index 0000000000..4da63e37b6 --- /dev/null +++ b/docs/es-ES/1.1.3/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.3

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/site-creation.html b/docs/es-ES/1.1.3/site-creation.html new file mode 100644 index 0000000000..04ec58b0a0 --- /dev/null +++ b/docs/es-ES/1.1.3/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.3

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/site-creation/index.html b/docs/es-ES/1.1.3/site-creation/index.html new file mode 100644 index 0000000000..04ec58b0a0 --- /dev/null +++ b/docs/es-ES/1.1.3/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.3

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/site-preparation.html b/docs/es-ES/1.1.3/site-preparation.html new file mode 100644 index 0000000000..81b010e578 --- /dev/null +++ b/docs/es-ES/1.1.3/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.3

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/site-preparation/index.html b/docs/es-ES/1.1.3/site-preparation/index.html new file mode 100644 index 0000000000..81b010e578 --- /dev/null +++ b/docs/es-ES/1.1.3/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.3

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/translation.html b/docs/es-ES/1.1.3/translation.html new file mode 100644 index 0000000000..4abd149d75 --- /dev/null +++ b/docs/es-ES/1.1.3/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.3

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/translation/index.html b/docs/es-ES/1.1.3/translation/index.html new file mode 100644 index 0000000000..4abd149d75 --- /dev/null +++ b/docs/es-ES/1.1.3/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.3

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/versioning.html b/docs/es-ES/1.1.3/versioning.html new file mode 100644 index 0000000000..669b7443d7 --- /dev/null +++ b/docs/es-ES/1.1.3/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.3

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.3/versioning/index.html b/docs/es-ES/1.1.3/versioning/index.html new file mode 100644 index 0000000000..669b7443d7 --- /dev/null +++ b/docs/es-ES/1.1.3/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.3

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/api-pages.html b/docs/es-ES/1.1.4/api-pages.html new file mode 100644 index 0000000000..ad5f9d45fa --- /dev/null +++ b/docs/es-ES/1.1.4/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.4

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/api-pages/index.html b/docs/es-ES/1.1.4/api-pages/index.html new file mode 100644 index 0000000000..ad5f9d45fa --- /dev/null +++ b/docs/es-ES/1.1.4/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.4

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/blog.html b/docs/es-ES/1.1.4/blog.html new file mode 100644 index 0000000000..430366f136 --- /dev/null +++ b/docs/es-ES/1.1.4/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.4

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/blog/index.html b/docs/es-ES/1.1.4/blog/index.html new file mode 100644 index 0000000000..430366f136 --- /dev/null +++ b/docs/es-ES/1.1.4/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.4

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/commands.html b/docs/es-ES/1.1.4/commands.html new file mode 100644 index 0000000000..81e2d9f2a7 --- /dev/null +++ b/docs/es-ES/1.1.4/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.4

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/commands/index.html b/docs/es-ES/1.1.4/commands/index.html new file mode 100644 index 0000000000..81e2d9f2a7 --- /dev/null +++ b/docs/es-ES/1.1.4/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.4

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/custom-pages.html b/docs/es-ES/1.1.4/custom-pages.html new file mode 100644 index 0000000000..511e457aa2 --- /dev/null +++ b/docs/es-ES/1.1.4/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.4

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/custom-pages/index.html b/docs/es-ES/1.1.4/custom-pages/index.html new file mode 100644 index 0000000000..511e457aa2 --- /dev/null +++ b/docs/es-ES/1.1.4/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.4

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/doc-markdown.html b/docs/es-ES/1.1.4/doc-markdown.html new file mode 100644 index 0000000000..f399020570 --- /dev/null +++ b/docs/es-ES/1.1.4/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.4

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/doc-markdown/index.html b/docs/es-ES/1.1.4/doc-markdown/index.html new file mode 100644 index 0000000000..f399020570 --- /dev/null +++ b/docs/es-ES/1.1.4/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.4

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/installation.html b/docs/es-ES/1.1.4/installation.html new file mode 100644 index 0000000000..9b27fef77a --- /dev/null +++ b/docs/es-ES/1.1.4/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.4

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/installation/index.html b/docs/es-ES/1.1.4/installation/index.html new file mode 100644 index 0000000000..9b27fef77a --- /dev/null +++ b/docs/es-ES/1.1.4/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.4

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/navigation.html b/docs/es-ES/1.1.4/navigation.html new file mode 100644 index 0000000000..4d06ff1319 --- /dev/null +++ b/docs/es-ES/1.1.4/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.4

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/navigation/index.html b/docs/es-ES/1.1.4/navigation/index.html new file mode 100644 index 0000000000..4d06ff1319 --- /dev/null +++ b/docs/es-ES/1.1.4/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.4

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/publishing.html b/docs/es-ES/1.1.4/publishing.html new file mode 100644 index 0000000000..a381f01433 --- /dev/null +++ b/docs/es-ES/1.1.4/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.4

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/publishing/index.html b/docs/es-ES/1.1.4/publishing/index.html new file mode 100644 index 0000000000..a381f01433 --- /dev/null +++ b/docs/es-ES/1.1.4/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.4

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/search.html b/docs/es-ES/1.1.4/search.html new file mode 100644 index 0000000000..16b0f2f7c8 --- /dev/null +++ b/docs/es-ES/1.1.4/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.4

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/search/index.html b/docs/es-ES/1.1.4/search/index.html new file mode 100644 index 0000000000..16b0f2f7c8 --- /dev/null +++ b/docs/es-ES/1.1.4/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.4

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/site-config.html b/docs/es-ES/1.1.4/site-config.html new file mode 100644 index 0000000000..9fdb8604e7 --- /dev/null +++ b/docs/es-ES/1.1.4/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.4

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/site-config/index.html b/docs/es-ES/1.1.4/site-config/index.html new file mode 100644 index 0000000000..9fdb8604e7 --- /dev/null +++ b/docs/es-ES/1.1.4/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.4

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/site-creation.html b/docs/es-ES/1.1.4/site-creation.html new file mode 100644 index 0000000000..9ef66103bd --- /dev/null +++ b/docs/es-ES/1.1.4/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.4

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/site-creation/index.html b/docs/es-ES/1.1.4/site-creation/index.html new file mode 100644 index 0000000000..9ef66103bd --- /dev/null +++ b/docs/es-ES/1.1.4/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.4

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/site-preparation.html b/docs/es-ES/1.1.4/site-preparation.html new file mode 100644 index 0000000000..ece03716d4 --- /dev/null +++ b/docs/es-ES/1.1.4/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.4

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/site-preparation/index.html b/docs/es-ES/1.1.4/site-preparation/index.html new file mode 100644 index 0000000000..ece03716d4 --- /dev/null +++ b/docs/es-ES/1.1.4/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.4

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/translation.html b/docs/es-ES/1.1.4/translation.html new file mode 100644 index 0000000000..497486cd8d --- /dev/null +++ b/docs/es-ES/1.1.4/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.4

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/translation/index.html b/docs/es-ES/1.1.4/translation/index.html new file mode 100644 index 0000000000..497486cd8d --- /dev/null +++ b/docs/es-ES/1.1.4/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.4

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/versioning.html b/docs/es-ES/1.1.4/versioning.html new file mode 100644 index 0000000000..2b38e1cfd3 --- /dev/null +++ b/docs/es-ES/1.1.4/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.4

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.4/versioning/index.html b/docs/es-ES/1.1.4/versioning/index.html new file mode 100644 index 0000000000..2b38e1cfd3 --- /dev/null +++ b/docs/es-ES/1.1.4/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.4

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/api-pages.html b/docs/es-ES/1.1.5/api-pages.html new file mode 100644 index 0000000000..d3223ed551 --- /dev/null +++ b/docs/es-ES/1.1.5/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.5

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/api-pages/index.html b/docs/es-ES/1.1.5/api-pages/index.html new file mode 100644 index 0000000000..d3223ed551 --- /dev/null +++ b/docs/es-ES/1.1.5/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.5

Translate

Pages and Styles

Docusaurus proporciona soporte para escribir páginas como componentes React dentro de la carpeta de sitio web/páginas la cual compartirá la misma cabecera, pie de página y estilos del resto del sitio.

+

URLs for Pages

+

Cualquier archivo .js en website/pages será renderizado como html estático usando la ruta del archivo despues de "pages". Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. Por ejemplo, la página para el archivo website/pages/en/help.js se encuentra en la url ${baseUrl}en/help.js, así como la dirección url ${baseUrl}help.js, donde ${baseUrl} es el campo baseUrl colocado en archivo siteConfig.js.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/blog.html b/docs/es-ES/1.1.5/blog.html new file mode 100644 index 0000000000..5f46a4e496 --- /dev/null +++ b/docs/es-ES/1.1.5/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.5

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/blog/index.html b/docs/es-ES/1.1.5/blog/index.html new file mode 100644 index 0000000000..5f46a4e496 --- /dev/null +++ b/docs/es-ES/1.1.5/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.5

Translate

Adding a Blog

Configuración inicial

+

Para configurar el sitio de su blog, comience por crear una carpeta blog en el directorio website de su repositorio.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Utilice el marcador <!--truncate--> en su publicación de blog para representar lo que se mostrará como el resumen al visualizar todas las publicaciones de blog publicadas en el blog. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/commands.html b/docs/es-ES/1.1.5/commands.html new file mode 100644 index 0000000000..312fb50b61 --- /dev/null +++ b/docs/es-ES/1.1.5/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.5

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/commands/index.html b/docs/es-ES/1.1.5/commands/index.html new file mode 100644 index 0000000000..312fb50b61 --- /dev/null +++ b/docs/es-ES/1.1.5/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.5

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: El usuario de git que se asociará con la implementación del commit.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/custom-pages.html b/docs/es-ES/1.1.5/custom-pages.html new file mode 100644 index 0000000000..c2bcca5cd2 --- /dev/null +++ b/docs/es-ES/1.1.5/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.5

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/custom-pages/index.html b/docs/es-ES/1.1.5/custom-pages/index.html new file mode 100644 index 0000000000..c2bcca5cd2 --- /dev/null +++ b/docs/es-ES/1.1.5/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.5

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternativamente, pueden colocarse en la carpeta pages y se servirían tal como están en lugar de representarse desde React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/doc-markdown.html b/docs/es-ES/1.1.5/doc-markdown.html new file mode 100644 index 0000000000..6f09dc80c2 --- /dev/null +++ b/docs/es-ES/1.1.5/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.5

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/doc-markdown/index.html b/docs/es-ES/1.1.5/doc-markdown/index.html new file mode 100644 index 0000000000..6f09dc80c2 --- /dev/null +++ b/docs/es-ES/1.1.5/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.1.5

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Las publicaciones del blog usan los siguientes campos de cabecera encerrados por una línea --- a cada lado:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

Se pueden utilizar urls relativos a otros archivos de documentación que se convertirán automáticamente a los enlaces html correspondientes cuando sean renderizados.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

Esto puede ayudar cuando se quiere navegar a través de docs en GitHub, ya que los enlaces de allí serán enlaces operativos que llevarán al usuario a otros documentos (ubicados en GitHub). Los documentos tendrán los enlaces html correctos cuando sean renderizados.

+

Enlazar a imágenes y otros recursos

+

Los recursos estáticos pueden ser enlazados de la misma manera que los documentos, usando las urls relativas. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

Se puede hacer una lista que genere enlaces automáticamente, la cual puede ser útil como una tabla de contenidos para documentación API.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/installation.html b/docs/es-ES/1.1.5/installation.html new file mode 100644 index 0000000000..8fa4701289 --- /dev/null +++ b/docs/es-ES/1.1.5/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.5

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/installation/index.html b/docs/es-ES/1.1.5/installation/index.html new file mode 100644 index 0000000000..8fa4701289 --- /dev/null +++ b/docs/es-ES/1.1.5/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.5

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/navigation.html b/docs/es-ES/1.1.5/navigation.html new file mode 100644 index 0000000000..7386862b06 --- /dev/null +++ b/docs/es-ES/1.1.5/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.5

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/navigation/index.html b/docs/es-ES/1.1.5/navigation/index.html new file mode 100644 index 0000000000..7386862b06 --- /dev/null +++ b/docs/es-ES/1.1.5/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.5

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/publishing.html b/docs/es-ES/1.1.5/publishing.html new file mode 100644 index 0000000000..bd8c0bb099 --- /dev/null +++ b/docs/es-ES/1.1.5/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.5

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/publishing/index.html b/docs/es-ES/1.1.5/publishing/index.html new file mode 100644 index 0000000000..bd8c0bb099 --- /dev/null +++ b/docs/es-ES/1.1.5/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.5

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/search.html b/docs/es-ES/1.1.5/search.html new file mode 100644 index 0000000000..907a1948f0 --- /dev/null +++ b/docs/es-ES/1.1.5/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.5

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/search/index.html b/docs/es-ES/1.1.5/search/index.html new file mode 100644 index 0000000000..907a1948f0 --- /dev/null +++ b/docs/es-ES/1.1.5/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.5

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/site-config.html b/docs/es-ES/1.1.5/site-config.html new file mode 100644 index 0000000000..8b27fc4ef4 --- /dev/null +++ b/docs/es-ES/1.1.5/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.5

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/site-config/index.html b/docs/es-ES/1.1.5/site-config/index.html new file mode 100644 index 0000000000..8b27fc4ef4 --- /dev/null +++ b/docs/es-ES/1.1.5/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.5

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - url para el favicon del sitio.

+

headerIcon - url para el icono utilizado en la barra de navegación del encabezado.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - url for your site.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/site-creation.html b/docs/es-ES/1.1.5/site-creation.html new file mode 100644 index 0000000000..20c5980aa3 --- /dev/null +++ b/docs/es-ES/1.1.5/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.5

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/site-creation/index.html b/docs/es-ES/1.1.5/site-creation/index.html new file mode 100644 index 0000000000..20c5980aa3 --- /dev/null +++ b/docs/es-ES/1.1.5/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.5

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Coloque activos, como imágenes, en la carpetawebsite/static/.

    6. +

  6. Ejecute el sitio para ver los resultados de sus cambios.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/site-preparation.html b/docs/es-ES/1.1.5/site-preparation.html new file mode 100644 index 0000000000..e27e14374a --- /dev/null +++ b/docs/es-ES/1.1.5/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.5

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/site-preparation/index.html b/docs/es-ES/1.1.5/site-preparation/index.html new file mode 100644 index 0000000000..e27e14374a --- /dev/null +++ b/docs/es-ES/1.1.5/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.5

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • La carpeta website/blog-examples-from-docusaurus contiene ejemplos de publicaciones de blog escritas en markdown.
    • +
  • La carpeta docs-examples-from-docusaurus contiene ejemplos de archivos de documentación escritos en markdown.
    • +
  • La carpeta website/pages contiene páginas de ejemplo de nivel superior para el sitio.
    • +
  • La carpeta website/static contiene recursos estáticos utilizados por el sitio de ejemplo.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

Debe mantener las carpetas website/pages y website/static, pero puede cambiar el contenido dentro de ellas como desee. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/translation.html b/docs/es-ES/1.1.5/translation.html new file mode 100644 index 0000000000..fb0c3ccd06 --- /dev/null +++ b/docs/es-ES/1.1.5/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.5

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/translation/index.html b/docs/es-ES/1.1.5/translation/index.html new file mode 100644 index 0000000000..fb0c3ccd06 --- /dev/null +++ b/docs/es-ES/1.1.5/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.5

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Las páginas con texto que desee traducir deben colocarse en la carpeta website/pages/en.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/versioning.html b/docs/es-ES/1.1.5/versioning.html new file mode 100644 index 0000000000..44894692b9 --- /dev/null +++ b/docs/es-ES/1.1.5/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.5

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.1.5/versioning/index.html b/docs/es-ES/1.1.5/versioning/index.html new file mode 100644 index 0000000000..44894692b9 --- /dev/null +++ b/docs/es-ES/1.1.5/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.5

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Ese conjunto específico de documentación se conservará y se podrá acceder incluso cuando la documentación en la carpeta docs cambie en adelante.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Esto conservará todos los documentos actualmente en la carpeta docs y los pondrá a disposición como documentación para la versión 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Los documentos en la carpeta docs se considerarán parte de la versión next y estarán disponibles, por ejemplo, en url docs/next/doc1.html. Los documentos de la última versión usan url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Los documentos de la versión 1.0.0 usarán la url docs/1.0.0/doc1.html mientras que 2.0.0 usará docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/api-pages.html b/docs/es-ES/1.2.0/api-pages.html new file mode 100644 index 0000000000..1ddbd4461b --- /dev/null +++ b/docs/es-ES/1.2.0/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/api-pages/index.html b/docs/es-ES/1.2.0/api-pages/index.html new file mode 100644 index 0000000000..1ddbd4461b --- /dev/null +++ b/docs/es-ES/1.2.0/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/blog.html b/docs/es-ES/1.2.0/blog.html new file mode 100644 index 0000000000..9300ea94ac --- /dev/null +++ b/docs/es-ES/1.2.0/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.2.0

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/blog/index.html b/docs/es-ES/1.2.0/blog/index.html new file mode 100644 index 0000000000..9300ea94ac --- /dev/null +++ b/docs/es-ES/1.2.0/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.2.0

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/commands.html b/docs/es-ES/1.2.0/commands.html new file mode 100644 index 0000000000..e1847b8ba8 --- /dev/null +++ b/docs/es-ES/1.2.0/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.2.0

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/commands/index.html b/docs/es-ES/1.2.0/commands/index.html new file mode 100644 index 0000000000..e1847b8ba8 --- /dev/null +++ b/docs/es-ES/1.2.0/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.2.0

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/custom-pages.html b/docs/es-ES/1.2.0/custom-pages.html new file mode 100644 index 0000000000..d2849a634f --- /dev/null +++ b/docs/es-ES/1.2.0/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/custom-pages/index.html b/docs/es-ES/1.2.0/custom-pages/index.html new file mode 100644 index 0000000000..d2849a634f --- /dev/null +++ b/docs/es-ES/1.2.0/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/doc-markdown.html b/docs/es-ES/1.2.0/doc-markdown.html new file mode 100644 index 0000000000..289cc1bbcf --- /dev/null +++ b/docs/es-ES/1.2.0/doc-markdown.html @@ -0,0 +1,187 @@ +Markdown Features · Docusaurus

1.2.0

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/doc-markdown/index.html b/docs/es-ES/1.2.0/doc-markdown/index.html new file mode 100644 index 0000000000..289cc1bbcf --- /dev/null +++ b/docs/es-ES/1.2.0/doc-markdown/index.html @@ -0,0 +1,187 @@ +Markdown Features · Docusaurus

1.2.0

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/installation.html b/docs/es-ES/1.2.0/installation.html new file mode 100644 index 0000000000..b9fc39f75d --- /dev/null +++ b/docs/es-ES/1.2.0/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.2.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/installation/index.html b/docs/es-ES/1.2.0/installation/index.html new file mode 100644 index 0000000000..b9fc39f75d --- /dev/null +++ b/docs/es-ES/1.2.0/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.2.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/navigation.html b/docs/es-ES/1.2.0/navigation.html new file mode 100644 index 0000000000..a557147496 --- /dev/null +++ b/docs/es-ES/1.2.0/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/navigation/index.html b/docs/es-ES/1.2.0/navigation/index.html new file mode 100644 index 0000000000..a557147496 --- /dev/null +++ b/docs/es-ES/1.2.0/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/publishing.html b/docs/es-ES/1.2.0/publishing.html new file mode 100644 index 0000000000..374138439f --- /dev/null +++ b/docs/es-ES/1.2.0/publishing.html @@ -0,0 +1,255 @@ +Publishing your site · Docusaurus

1.2.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/publishing/index.html b/docs/es-ES/1.2.0/publishing/index.html new file mode 100644 index 0000000000..374138439f --- /dev/null +++ b/docs/es-ES/1.2.0/publishing/index.html @@ -0,0 +1,255 @@ +Publishing your site · Docusaurus

1.2.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/search.html b/docs/es-ES/1.2.0/search.html new file mode 100644 index 0000000000..867b1e4845 --- /dev/null +++ b/docs/es-ES/1.2.0/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.2.0

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/search/index.html b/docs/es-ES/1.2.0/search/index.html new file mode 100644 index 0000000000..867b1e4845 --- /dev/null +++ b/docs/es-ES/1.2.0/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.2.0

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/site-config.html b/docs/es-ES/1.2.0/site-config.html new file mode 100644 index 0000000000..c59db8a8c3 --- /dev/null +++ b/docs/es-ES/1.2.0/site-config.html @@ -0,0 +1,257 @@ +siteConfig.js · Docusaurus

1.2.0

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/site-config/index.html b/docs/es-ES/1.2.0/site-config/index.html new file mode 100644 index 0000000000..c59db8a8c3 --- /dev/null +++ b/docs/es-ES/1.2.0/site-config/index.html @@ -0,0 +1,257 @@ +siteConfig.js · Docusaurus

1.2.0

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/site-creation.html b/docs/es-ES/1.2.0/site-creation.html new file mode 100644 index 0000000000..655b8e23a4 --- /dev/null +++ b/docs/es-ES/1.2.0/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/site-creation/index.html b/docs/es-ES/1.2.0/site-creation/index.html new file mode 100644 index 0000000000..655b8e23a4 --- /dev/null +++ b/docs/es-ES/1.2.0/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/site-preparation.html b/docs/es-ES/1.2.0/site-preparation.html new file mode 100644 index 0000000000..0cb76adc31 --- /dev/null +++ b/docs/es-ES/1.2.0/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/site-preparation/index.html b/docs/es-ES/1.2.0/site-preparation/index.html new file mode 100644 index 0000000000..0cb76adc31 --- /dev/null +++ b/docs/es-ES/1.2.0/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/translation.html b/docs/es-ES/1.2.0/translation.html new file mode 100644 index 0000000000..88b3817abe --- /dev/null +++ b/docs/es-ES/1.2.0/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.2.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/translation/index.html b/docs/es-ES/1.2.0/translation/index.html new file mode 100644 index 0000000000..88b3817abe --- /dev/null +++ b/docs/es-ES/1.2.0/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.2.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/versioning.html b/docs/es-ES/1.2.0/versioning.html new file mode 100644 index 0000000000..ade2a83093 --- /dev/null +++ b/docs/es-ES/1.2.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.2.0/versioning/index.html b/docs/es-ES/1.2.0/versioning/index.html new file mode 100644 index 0000000000..ade2a83093 --- /dev/null +++ b/docs/es-ES/1.2.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/api-pages.html b/docs/es-ES/1.2.1/api-pages.html new file mode 100644 index 0000000000..c37c278c24 --- /dev/null +++ b/docs/es-ES/1.2.1/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/api-pages/index.html b/docs/es-ES/1.2.1/api-pages/index.html new file mode 100644 index 0000000000..c37c278c24 --- /dev/null +++ b/docs/es-ES/1.2.1/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/blog.html b/docs/es-ES/1.2.1/blog.html new file mode 100644 index 0000000000..ae2adb42e3 --- /dev/null +++ b/docs/es-ES/1.2.1/blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.2.1

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/blog/index.html b/docs/es-ES/1.2.1/blog/index.html new file mode 100644 index 0000000000..ae2adb42e3 --- /dev/null +++ b/docs/es-ES/1.2.1/blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.2.1

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/commands.html b/docs/es-ES/1.2.1/commands.html new file mode 100644 index 0000000000..1d8a16e553 --- /dev/null +++ b/docs/es-ES/1.2.1/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.2.1

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/commands/index.html b/docs/es-ES/1.2.1/commands/index.html new file mode 100644 index 0000000000..1d8a16e553 --- /dev/null +++ b/docs/es-ES/1.2.1/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.2.1

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/custom-pages.html b/docs/es-ES/1.2.1/custom-pages.html new file mode 100644 index 0000000000..ea48bed7b3 --- /dev/null +++ b/docs/es-ES/1.2.1/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/custom-pages/index.html b/docs/es-ES/1.2.1/custom-pages/index.html new file mode 100644 index 0000000000..ea48bed7b3 --- /dev/null +++ b/docs/es-ES/1.2.1/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← AnteriorEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/doc-markdown.html b/docs/es-ES/1.2.1/doc-markdown.html new file mode 100644 index 0000000000..2c24c76c83 --- /dev/null +++ b/docs/es-ES/1.2.1/doc-markdown.html @@ -0,0 +1,187 @@ +Markdown Features · Docusaurus

1.2.1

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/doc-markdown/index.html b/docs/es-ES/1.2.1/doc-markdown/index.html new file mode 100644 index 0000000000..2c24c76c83 --- /dev/null +++ b/docs/es-ES/1.2.1/doc-markdown/index.html @@ -0,0 +1,187 @@ +Markdown Features · Docusaurus

1.2.1

Translate

Markdown Features

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/installation.html b/docs/es-ES/1.2.1/installation.html new file mode 100644 index 0000000000..2f5afc5f62 --- /dev/null +++ b/docs/es-ES/1.2.1/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.2.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/installation/index.html b/docs/es-ES/1.2.1/installation/index.html new file mode 100644 index 0000000000..2f5afc5f62 --- /dev/null +++ b/docs/es-ES/1.2.1/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.2.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/navigation.html b/docs/es-ES/1.2.1/navigation.html new file mode 100644 index 0000000000..2291cfe2a4 --- /dev/null +++ b/docs/es-ES/1.2.1/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/navigation/index.html b/docs/es-ES/1.2.1/navigation/index.html new file mode 100644 index 0000000000..2291cfe2a4 --- /dev/null +++ b/docs/es-ES/1.2.1/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/publishing.html b/docs/es-ES/1.2.1/publishing.html new file mode 100644 index 0000000000..5d6b95da27 --- /dev/null +++ b/docs/es-ES/1.2.1/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.2.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/publishing/index.html b/docs/es-ES/1.2.1/publishing/index.html new file mode 100644 index 0000000000..5d6b95da27 --- /dev/null +++ b/docs/es-ES/1.2.1/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.2.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSiguiente →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/search.html b/docs/es-ES/1.2.1/search.html new file mode 100644 index 0000000000..d82f1193b0 --- /dev/null +++ b/docs/es-ES/1.2.1/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.2.1

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/search/index.html b/docs/es-ES/1.2.1/search/index.html new file mode 100644 index 0000000000..d82f1193b0 --- /dev/null +++ b/docs/es-ES/1.2.1/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.2.1

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/site-config.html b/docs/es-ES/1.2.1/site-config.html new file mode 100644 index 0000000000..6a31c5085a --- /dev/null +++ b/docs/es-ES/1.2.1/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.2.1

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/site-config/index.html b/docs/es-ES/1.2.1/site-config/index.html new file mode 100644 index 0000000000..6a31c5085a --- /dev/null +++ b/docs/es-ES/1.2.1/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.2.1

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/site-creation.html b/docs/es-ES/1.2.1/site-creation.html new file mode 100644 index 0000000000..83cc391f77 --- /dev/null +++ b/docs/es-ES/1.2.1/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/site-creation/index.html b/docs/es-ES/1.2.1/site-creation/index.html new file mode 100644 index 0000000000..83cc391f77 --- /dev/null +++ b/docs/es-ES/1.2.1/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/site-preparation.html b/docs/es-ES/1.2.1/site-preparation.html new file mode 100644 index 0000000000..cb27b997fb --- /dev/null +++ b/docs/es-ES/1.2.1/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/site-preparation/index.html b/docs/es-ES/1.2.1/site-preparation/index.html new file mode 100644 index 0000000000..cb27b997fb --- /dev/null +++ b/docs/es-ES/1.2.1/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/translation.html b/docs/es-ES/1.2.1/translation.html new file mode 100644 index 0000000000..0a030d9d81 --- /dev/null +++ b/docs/es-ES/1.2.1/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.2.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/translation/index.html b/docs/es-ES/1.2.1/translation/index.html new file mode 100644 index 0000000000..0a030d9d81 --- /dev/null +++ b/docs/es-ES/1.2.1/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.2.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/versioning.html b/docs/es-ES/1.2.1/versioning.html new file mode 100644 index 0000000000..1ade0fa016 --- /dev/null +++ b/docs/es-ES/1.2.1/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.2.1/versioning/index.html b/docs/es-ES/1.2.1/versioning/index.html new file mode 100644 index 0000000000..1ade0fa016 --- /dev/null +++ b/docs/es-ES/1.2.1/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/adding-blog.html b/docs/es-ES/1.3.0/adding-blog.html new file mode 100644 index 0000000000..764c72d0d1 --- /dev/null +++ b/docs/es-ES/1.3.0/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/adding-blog/index.html b/docs/es-ES/1.3.0/adding-blog/index.html new file mode 100644 index 0000000000..764c72d0d1 --- /dev/null +++ b/docs/es-ES/1.3.0/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/api-pages.html b/docs/es-ES/1.3.0/api-pages.html new file mode 100644 index 0000000000..c5fbcf38b9 --- /dev/null +++ b/docs/es-ES/1.3.0/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/api-pages/index.html b/docs/es-ES/1.3.0/api-pages/index.html new file mode 100644 index 0000000000..c5fbcf38b9 --- /dev/null +++ b/docs/es-ES/1.3.0/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/blog.html b/docs/es-ES/1.3.0/blog.html new file mode 100644 index 0000000000..127feb4f77 --- /dev/null +++ b/docs/es-ES/1.3.0/blog.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/blog/index.html b/docs/es-ES/1.3.0/blog/index.html new file mode 100644 index 0000000000..127feb4f77 --- /dev/null +++ b/docs/es-ES/1.3.0/blog/index.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/commands.html b/docs/es-ES/1.3.0/commands.html new file mode 100644 index 0000000000..3cf75158a2 --- /dev/null +++ b/docs/es-ES/1.3.0/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.0

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/commands/index.html b/docs/es-ES/1.3.0/commands/index.html new file mode 100644 index 0000000000..3cf75158a2 --- /dev/null +++ b/docs/es-ES/1.3.0/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.0

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/custom-pages.html b/docs/es-ES/1.3.0/custom-pages.html new file mode 100644 index 0000000000..6dfe0e142e --- /dev/null +++ b/docs/es-ES/1.3.0/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/custom-pages/index.html b/docs/es-ES/1.3.0/custom-pages/index.html new file mode 100644 index 0000000000..6dfe0e142e --- /dev/null +++ b/docs/es-ES/1.3.0/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/doc-markdown.html b/docs/es-ES/1.3.0/doc-markdown.html new file mode 100644 index 0000000000..260e1207cd --- /dev/null +++ b/docs/es-ES/1.3.0/doc-markdown.html @@ -0,0 +1,188 @@ +Markdown Features · Docusaurus

1.3.0

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/doc-markdown/index.html b/docs/es-ES/1.3.0/doc-markdown/index.html new file mode 100644 index 0000000000..260e1207cd --- /dev/null +++ b/docs/es-ES/1.3.0/doc-markdown/index.html @@ -0,0 +1,188 @@ +Markdown Features · Docusaurus

1.3.0

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/installation.html b/docs/es-ES/1.3.0/installation.html new file mode 100644 index 0000000000..d994b260da --- /dev/null +++ b/docs/es-ES/1.3.0/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/installation/index.html b/docs/es-ES/1.3.0/installation/index.html new file mode 100644 index 0000000000..d994b260da --- /dev/null +++ b/docs/es-ES/1.3.0/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/navigation.html b/docs/es-ES/1.3.0/navigation.html new file mode 100644 index 0000000000..3a16671a28 --- /dev/null +++ b/docs/es-ES/1.3.0/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/navigation/index.html b/docs/es-ES/1.3.0/navigation/index.html new file mode 100644 index 0000000000..3a16671a28 --- /dev/null +++ b/docs/es-ES/1.3.0/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/publishing.html b/docs/es-ES/1.3.0/publishing.html new file mode 100644 index 0000000000..ad73000c93 --- /dev/null +++ b/docs/es-ES/1.3.0/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/publishing/index.html b/docs/es-ES/1.3.0/publishing/index.html new file mode 100644 index 0000000000..ad73000c93 --- /dev/null +++ b/docs/es-ES/1.3.0/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/search.html b/docs/es-ES/1.3.0/search.html new file mode 100644 index 0000000000..29ec65cda7 --- /dev/null +++ b/docs/es-ES/1.3.0/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.0

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/search/index.html b/docs/es-ES/1.3.0/search/index.html new file mode 100644 index 0000000000..29ec65cda7 --- /dev/null +++ b/docs/es-ES/1.3.0/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.0

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/site-config.html b/docs/es-ES/1.3.0/site-config.html new file mode 100644 index 0000000000..caad16c7e8 --- /dev/null +++ b/docs/es-ES/1.3.0/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.0

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/site-config/index.html b/docs/es-ES/1.3.0/site-config/index.html new file mode 100644 index 0000000000..caad16c7e8 --- /dev/null +++ b/docs/es-ES/1.3.0/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.0

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/site-creation.html b/docs/es-ES/1.3.0/site-creation.html new file mode 100644 index 0000000000..fdd4270f3f --- /dev/null +++ b/docs/es-ES/1.3.0/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/site-creation/index.html b/docs/es-ES/1.3.0/site-creation/index.html new file mode 100644 index 0000000000..fdd4270f3f --- /dev/null +++ b/docs/es-ES/1.3.0/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/site-preparation.html b/docs/es-ES/1.3.0/site-preparation.html new file mode 100644 index 0000000000..8c42068d50 --- /dev/null +++ b/docs/es-ES/1.3.0/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/site-preparation/index.html b/docs/es-ES/1.3.0/site-preparation/index.html new file mode 100644 index 0000000000..8c42068d50 --- /dev/null +++ b/docs/es-ES/1.3.0/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/translation.html b/docs/es-ES/1.3.0/translation.html new file mode 100644 index 0000000000..36834791f1 --- /dev/null +++ b/docs/es-ES/1.3.0/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/translation/index.html b/docs/es-ES/1.3.0/translation/index.html new file mode 100644 index 0000000000..36834791f1 --- /dev/null +++ b/docs/es-ES/1.3.0/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/versioning.html b/docs/es-ES/1.3.0/versioning.html new file mode 100644 index 0000000000..aa4597ad65 --- /dev/null +++ b/docs/es-ES/1.3.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/1.3.0/versioning/index.html b/docs/es-ES/1.3.0/versioning/index.html new file mode 100644 index 0000000000..aa4597ad65 --- /dev/null +++ b/docs/es-ES/1.3.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/adding-blog.html b/docs/es-ES/adding-blog.html new file mode 100644 index 0000000000..f4c73146d9 --- /dev/null +++ b/docs/es-ES/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/adding-blog/index.html b/docs/es-ES/adding-blog/index.html new file mode 100644 index 0000000000..f4c73146d9 --- /dev/null +++ b/docs/es-ES/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/api-pages.html b/docs/es-ES/api-pages.html new file mode 100644 index 0000000000..3452b09875 --- /dev/null +++ b/docs/es-ES/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/api-pages/index.html b/docs/es-ES/api-pages/index.html new file mode 100644 index 0000000000..3452b09875 --- /dev/null +++ b/docs/es-ES/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/blog.html b/docs/es-ES/blog.html new file mode 100644 index 0000000000..be80299433 --- /dev/null +++ b/docs/es-ES/blog.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/es-ES/blog/index.html b/docs/es-ES/blog/index.html new file mode 100644 index 0000000000..be80299433 --- /dev/null +++ b/docs/es-ES/blog/index.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/es-ES/commands.html b/docs/es-ES/commands.html new file mode 100644 index 0000000000..5d03f22c40 --- /dev/null +++ b/docs/es-ES/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.1

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/commands/index.html b/docs/es-ES/commands/index.html new file mode 100644 index 0000000000..5d03f22c40 --- /dev/null +++ b/docs/es-ES/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.1

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/custom-pages.html b/docs/es-ES/custom-pages.html new file mode 100644 index 0000000000..c8e417e553 --- /dev/null +++ b/docs/es-ES/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/custom-pages/index.html b/docs/es-ES/custom-pages/index.html new file mode 100644 index 0000000000..c8e417e553 --- /dev/null +++ b/docs/es-ES/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/doc-markdown.html b/docs/es-ES/doc-markdown.html new file mode 100644 index 0000000000..338ca0d143 --- /dev/null +++ b/docs/es-ES/doc-markdown.html @@ -0,0 +1,188 @@ +Markdown Features · Docusaurus

1.3.1

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/doc-markdown/index.html b/docs/es-ES/doc-markdown/index.html new file mode 100644 index 0000000000..338ca0d143 --- /dev/null +++ b/docs/es-ES/doc-markdown/index.html @@ -0,0 +1,188 @@ +Markdown Features · Docusaurus

1.3.1

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/installation.html b/docs/es-ES/installation.html new file mode 100644 index 0000000000..f721de2218 --- /dev/null +++ b/docs/es-ES/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/installation/index.html b/docs/es-ES/installation/index.html new file mode 100644 index 0000000000..f721de2218 --- /dev/null +++ b/docs/es-ES/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/navigation.html b/docs/es-ES/navigation.html new file mode 100644 index 0000000000..c6e63e439e --- /dev/null +++ b/docs/es-ES/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/navigation/index.html b/docs/es-ES/navigation/index.html new file mode 100644 index 0000000000..c6e63e439e --- /dev/null +++ b/docs/es-ES/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/next/adding-blog.html b/docs/es-ES/next/adding-blog.html new file mode 100644 index 0000000000..fe31a9bf7b --- /dev/null +++ b/docs/es-ES/next/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

next

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/next/adding-blog/index.html b/docs/es-ES/next/adding-blog/index.html new file mode 100644 index 0000000000..fe31a9bf7b --- /dev/null +++ b/docs/es-ES/next/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

next

Translate

Adding a Blog

Configuración inicial

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Luego, agrega un enlace de encabezado a tu blog dentro de siteConfig.js:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Añadiendo un blog

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Por ejemplo, en website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Opciones de encabezado

+

El único campo obligatorio es title; sin embargo, brindamos opciones para agregar información del autor a la publicación de tu blog.

+
    +
  • author - La etiqueta de texto del autor por línea.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Plan de resumen

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Cualquier cosa sobre <!--truncate--> será parte del resumen. Por ejemplo:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Ejemplo:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Ejemplo:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/es-ES/next/api-pages.html b/docs/es-ES/next/api-pages.html new file mode 100644 index 0000000000..7d1040ab4f --- /dev/null +++ b/docs/es-ES/next/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

next

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/next/api-pages/index.html b/docs/es-ES/next/api-pages/index.html new file mode 100644 index 0000000000..7d1040ab4f --- /dev/null +++ b/docs/es-ES/next/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

next

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. Los archivos en website/pages/en serán copiados en pages e invalidará cualquier archivo con el mismo nombre en pages. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Ejemplo:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Ejemplo:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/es-ES/next/commands.html b/docs/es-ES/next/commands.html new file mode 100644 index 0000000000..a0de32489f --- /dev/null +++ b/docs/es-ES/next/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

next

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/next/commands/index.html b/docs/es-ES/next/commands/index.html new file mode 100644 index 0000000000..a0de32489f --- /dev/null +++ b/docs/es-ES/next/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

next

Translate

CLI Commands

Docusaurus proporciona un conjunto de scripts para ayudarlo a generar, abastecer e implementar su sitio web. Estos scripts se pueden invocar con el comando run cuando se utiliza Yarn o npm. Algunos comandos comunes son:

+ +

Ejecución desde la línea de comandos

+

Los scripts se pueden ejecutar usando Yarn o npm. Si ya ha consultado nuestra guía de introducción, es posible que ya esté familiarizado con el comando start. Es el comando que le dice a Docusaurus que ejecute el script docusaurus-start que genera el sitio y arranca un servidor, y generalmente se invoca así:

+
yarn run start
+
+

El mismo script puede invocarse usando npm:

+
npm run start
+
+

Para ejecutar un script en particular, simplemente reemplace el comando start en los ejemplos anteriores con el comando asociado con su script.

+

Usando argumentos

+

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
+
+

Si ejecuta Docusaurus utilizando npm, puede seguir utilizando los argumentos de la línea de comando insertando un -- entre npm run <command> y los argumentos del comando:

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

Configuración

+

Estos scripts se configuran con la clave "scripts" en su archivo website/package.json como parte del proceso de instalación. Si necesita ayuda para configurarlas nuevamente, consulte la Guía de instalación .

+

Docusaurus proporciona algunas asignaciones predeterminadas que le permiten ejecutar comandos siguiendo las convenciones de Nodo. En lugar de escribir docusaurus-start siempre, puede escribir yarn run start o npm start para lograr lo mismo.

+

Comandos

+

<autogenerated_table_of_contents>

+
+

Referencia

+

docusaurus-build

+

Alias: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Alias: examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: El usuario de git que se asociará con la implementación del commit.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: El branch del git asociada con el commit que desencadenó la ejecución del CI.
    • +
  • CI_PULL_REQUEST: Se espera que sea cierto si la ejecución de CI actual fue desencadenada por un commit en una solicitud de extracción.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/es-ES/next/custom-pages.html b/docs/es-ES/next/custom-pages.html new file mode 100644 index 0000000000..99e2a5f0dd --- /dev/null +++ b/docs/es-ES/next/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

next

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/next/custom-pages/index.html b/docs/es-ES/next/custom-pages/index.html new file mode 100644 index 0000000000..99e2a5f0dd --- /dev/null +++ b/docs/es-ES/next/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

next

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Personalizar tu página de inicio

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. A partir de ahí, edite el archivo website/pages/en/index.js y sus diversos componentes para usar las imágenes y el texto que desee para su proyecto.

+

Agregar otras páginas personalizadas

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Puede encontrar más información sobre cómo usar los componentes proporcionados o incluir la suya propia aquí . La información sobre cómo enlazar a sus diferentes páginas en la barra de navegación del encabezado se puede encontrar aquí .

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Agregar páginas estáticas

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Personalizar tu página de inicio

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

El ejemplo proporcionado tiene tres columnas con una imagen de pie de página a la izquierda y el logotipo de fuente abierta de Facebook y derechos de autor en la parte inferior. Si su proyecto no es un proyecto de código abierto de Facebook, elimine el logotipo y los derechos de autor. De lo contrario, ¡siéntete libre de ser creativo con tu pie de página y ¡haz que se vea como quieras!

+

Algunas sugerencias de enlaces que puede proporcionar: documentación, API, Twitter, Discordia, grupos de Facebook, Stack Overflow, GitHub, etc.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/es-ES/next/doc-markdown.html b/docs/es-ES/next/doc-markdown.html new file mode 100644 index 0000000000..0aec76255d --- /dev/null +++ b/docs/es-ES/next/doc-markdown.html @@ -0,0 +1,188 @@ +Markdown Features · Docusaurus

next

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/next/doc-markdown/index.html b/docs/es-ES/next/doc-markdown/index.html new file mode 100644 index 0000000000..0aec76255d --- /dev/null +++ b/docs/es-ES/next/doc-markdown/index.html @@ -0,0 +1,188 @@ +Markdown Features · Docusaurus

next

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Cabeceras de Markdown

+

Documentos

+

Los documentos usan los siguientes campos de cabecera encerrados por una línea de comando --- a cada lado:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Por ejemplo:

+
id: doc1
+title: Mi Documento
+sidebar_label: Documento
+
+

Las distintas versiones del documento tienen sus ids alterados para incluir el número de la versión cuando son copiados. El nuevo id es version-${version}-${id}, donde ${version} es el número de la versión del documento y ${id} es el id original. Además, a las versiones del documento se les añade un campo original_id junto al id del documento original.

+

Por ejemplo:

+
d: version-1.0.0-doc1
+title: Mi Documento
+sidebar_label: Documento
+original_id: doc1
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Por ejemplo:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog de publicaciones

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: el título de la publicación del blog.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: el id de Facebook del autor. Se usa solamente para mostrar la foto de perfil del autor con la publicación del blog. Si se omite este campo, no aparecerá la foto del autor en la publicación del post.

+

Por ejemplo:

+
title: Mi primera publicación
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+
+

Características adicionales

+

Docusaurus es compatible con algunas características adicionales al escribir documentación en markdown.

+

Enlazar otros documentos

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Ejemplo:

+
[Se enlaza con otro documento] (otro-documento.md)
+
+

Este markdown se convertirá automáticamente en un enlace /docs/other-document.html (o en un enlace adecuadamente traducido) cuando sea renderizado.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Enlazar a imágenes y otros recursos

+

Static assets can be linked to in the same way that documents are, using relative URLs. Los recursos estáticos utilizados en los documentos y blogs deben ir dentro de docs/assets y website/blog/assets, respectivamente. El markdown será convertido en las rutas de enlace correspondientes, y así estas rutas funcionarán para los documentos de todos los idiomas y versiones.

+

Ejemplo:

+
![alt-text](/docs/assets/doc-image.png)
+
+

Generar tabla de contenidos

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Escriba su documentación utilizando las cabeceras h3 para cada función dentro de un bloque de código. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Ejemplo:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

dirigirá a la tabla de contenido de las funciones:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

y cada función se enlazará a su sección correspondiente en la página.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Ejemplo:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/es-ES/next/installation.html b/docs/es-ES/next/installation.html new file mode 100644 index 0000000000..0ae153c69d --- /dev/null +++ b/docs/es-ES/next/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

next

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/next/installation/index.html b/docs/es-ES/next/installation/index.html new file mode 100644 index 0000000000..0ae153c69d --- /dev/null +++ b/docs/es-ES/next/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

next

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Verificar la instalación

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

o

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/es-ES/next/navigation.html b/docs/es-ES/next/navigation.html new file mode 100644 index 0000000000..68b1c13207 --- /dev/null +++ b/docs/es-ES/next/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

next

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/next/navigation/index.html b/docs/es-ES/next/navigation/index.html new file mode 100644 index 0000000000..68b1c13207 --- /dev/null +++ b/docs/es-ES/next/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

next

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

O puede crear una nueva categoría en la barra lateral:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Por ejemplo, si tenemos una página dentro de website/pages/help.js, podemos hacer un enlace agregando lo siguiente:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Para abrir enlaces externos en una nueva pestaña, proporcione un indicador external: true dentro de la configuración del enlace del encabezado.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Si la búsqueda está habilitada en su sitio, su barra de búsqueda aparecerá a la derecha de sus enlaces. Si desea colocar la barra de búsqueda entre los enlaces en el encabezado, agregue una entrada de búsqueda en la matriz de configuraciónheaderLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Si las traducciones están habilitadas en su sitio, el menú desplegable del idioma aparecerá a la derecha de sus enlaces (y a la izquierda de la barra de búsqueda, si la búsqueda está habilitada). Si desea colocar la selección de idioma desplegable entre los enlaces en el encabezado, agregue una entrada de idiomas en la matriz de configuración headerLinks:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/es-ES/next/publishing.html b/docs/es-ES/next/publishing.html new file mode 100644 index 0000000000..9f638da81a --- /dev/null +++ b/docs/es-ES/next/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

next

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/es-ES/next/publishing/index.html b/docs/es-ES/next/publishing/index.html new file mode 100644 index 0000000000..9f638da81a --- /dev/null +++ b/docs/es-ES/next/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

next

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/es-ES/next/search.html b/docs/es-ES/next/search.html new file mode 100644 index 0000000000..2cb67d178b --- /dev/null +++ b/docs/es-ES/next/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

next

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/next/search/index.html b/docs/es-ES/next/search/index.html new file mode 100644 index 0000000000..2cb67d178b --- /dev/null +++ b/docs/es-ES/next/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

next

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/next/site-config.html b/docs/es-ES/next/site-config.html new file mode 100644 index 0000000000..9bb7558250 --- /dev/null +++ b/docs/es-ES/next/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

next

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/next/site-config/index.html b/docs/es-ES/next/site-config/index.html new file mode 100644 index 0000000000..9bb7558250 --- /dev/null +++ b/docs/es-ES/next/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

next

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/next/site-creation.html b/docs/es-ES/next/site-creation.html new file mode 100644 index 0000000000..c8695ffb61 --- /dev/null +++ b/docs/es-ES/next/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

next

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/next/site-creation/index.html b/docs/es-ES/next/site-creation/index.html new file mode 100644 index 0000000000..c8695ffb61 --- /dev/null +++ b/docs/es-ES/next/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

next

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/next/site-preparation.html b/docs/es-ES/next/site-preparation.html new file mode 100644 index 0000000000..172f6c8295 --- /dev/null +++ b/docs/es-ES/next/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

next

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/next/site-preparation/index.html b/docs/es-ES/next/site-preparation/index.html new file mode 100644 index 0000000000..172f6c8295 --- /dev/null +++ b/docs/es-ES/next/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

next

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/next/translation.html b/docs/es-ES/next/translation.html new file mode 100644 index 0000000000..e562dce8ae --- /dev/null +++ b/docs/es-ES/next/translation.html @@ -0,0 +1,265 @@ +Translations and Localization · Docusaurus

next

Translate

Translations and Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/next/translation/index.html b/docs/es-ES/next/translation/index.html new file mode 100644 index 0000000000..e562dce8ae --- /dev/null +++ b/docs/es-ES/next/translation/index.html @@ -0,0 +1,265 @@ +Translations and Localization · Docusaurus

next

Translate

Translations and Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/next/versioning.html b/docs/es-ES/next/versioning.html new file mode 100644 index 0000000000..d6e1e73354 --- /dev/null +++ b/docs/es-ES/next/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

next

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/next/versioning/index.html b/docs/es-ES/next/versioning/index.html new file mode 100644 index 0000000000..d6e1e73354 --- /dev/null +++ b/docs/es-ES/next/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

next

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/publishing.html b/docs/es-ES/publishing.html new file mode 100644 index 0000000000..c5e8567d80 --- /dev/null +++ b/docs/es-ES/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/es-ES/publishing/index.html b/docs/es-ES/publishing/index.html new file mode 100644 index 0000000000..c5e8567d80 --- /dev/null +++ b/docs/es-ES/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/es-ES/search.html b/docs/es-ES/search.html new file mode 100644 index 0000000000..ec862f309a --- /dev/null +++ b/docs/es-ES/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.1

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/search/index.html b/docs/es-ES/search/index.html new file mode 100644 index 0000000000..ec862f309a --- /dev/null +++ b/docs/es-ES/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.1

Translate

Enabling Search

Docusaurus admite la búsqueda usando Algolia DocSearch. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Habilitando la barra de búsqueda

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/es-ES/site-config.html b/docs/es-ES/site-config.html new file mode 100644 index 0000000000..a1c44f702b --- /dev/null +++ b/docs/es-ES/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.1

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/site-config/index.html b/docs/es-ES/site-config/index.html new file mode 100644 index 0000000000..a1c44f702b --- /dev/null +++ b/docs/es-ES/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.1

Translate

siteConfig.js

Una gran parte de la configuración del sitio se realiza editando el archivo siteConfig.js.

+

Mostrador de usuarios

+

La matriz users se usa para almacenar objetos para cada proyecto/usuario que quiera mostrar en su sitio. Actualmente, este campo se utiliza, por ejemplo, con los archivos pages/en/index.js y pages/en/users.js. Cada objeto de usuario debe tener los campos caption, image, infoLink, ypinned. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. El campo pinned determina si se muestra o no en la página index.

+

Actualmente, esta orden users solo se usa con los archivos de ejemplo index.js y users.js. Si no desea tener una página de usuarios o mostrar usuarios en la página index, puede eliminar esta sección.

+

campos de configuración del sitio

+

El objeto siteConfig contiene la mayor parte de las configuraciones para su sitio web.

+

Campos obligatorios

+

baseUrl - Url base para su sitio.

+

colors - Configuraciones de color para el sitio.

+
    +
  • primaryColor es el color utilizado en la barra de navegación del encabezado y las barras laterales.
    • +
  • secondaryColor es el color que se ve en la segunda fila de la barra de navegación del encabezado cuando la ventana del sitio es estrecha (incluso en el móvil).
    • +
  • Las configuraciones de color personalizadas también se pueden agregar. Por ejemplo, si se agregan estilos de usuario con colores especificados como$myColor, agregar un campo myColor a colors le permitirá configurar fácilmente este color.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Ejemplo de uso:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Lema para su sitio web.

+

title - Título para su sitio web.

+

url - URL for your website.

+

Campos opcionales

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/es-ES/site-creation.html b/docs/es-ES/site-creation.html new file mode 100644 index 0000000000..3db5a97d61 --- /dev/null +++ b/docs/es-ES/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/site-creation/index.html b/docs/es-ES/site-creation/index.html new file mode 100644 index 0000000000..3db5a97d61 --- /dev/null +++ b/docs/es-ES/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Después de instalación y preparación, gran parte del trabajo para crear un sitio básico para tus documentos ya está completo.

+

Estructura del sitio

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Crea tu sitio básico

+

Para crear un sitio totalmente funcional, solo necesita hacer unos pocos pasos:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Si no agrega su documentación al archivo sidebars.json, los documentos se mostrarán, pero solo se pueden vincular desde otra documentación y se pueden visitar con la URL conocida.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Ejecute el sitio para ver los resultados de sus cambios.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/es-ES/site-preparation.html b/docs/es-ES/site-preparation.html new file mode 100644 index 0000000000..3fdaf9aa78 --- /dev/null +++ b/docs/es-ES/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/site-preparation/index.html b/docs/es-ES/site-preparation/index.html new file mode 100644 index 0000000000..3fdaf9aa78 --- /dev/null +++ b/docs/es-ES/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • El archivo website/core/Footer.js es un componente de reacción que actúa como el pie de página del sitio generado por Docusaurus y debe ser personalizado por el usuario.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • El archivo website/siteConfig.js es el archivo de configuración principal utilizado por Docusaurus.
    • +
+

Deberá conservar los archivos website/siteConfig.js y website/core/Footer.js, pero puede editarlos como desee.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. Como mínimo, debe tener un archivo en/index.js o en/index.htmlarchivo dentro. website/pages y una imagen para usar como su icono de encabezado dentro de website/static.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/es-ES/translation.html b/docs/es-ES/translation.html new file mode 100644 index 0000000000..31ba474d1e --- /dev/null +++ b/docs/es-ES/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/translation/index.html b/docs/es-ES/translation/index.html new file mode 100644 index 0000000000..31ba474d1e --- /dev/null +++ b/docs/es-ES/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. Los archivos de documentación escritos en inglés se cargan en Crowdin para su traducción por los usuarios de una comunidad. Las páginas de nivel superior escritas con cadenas en inglés se pueden traducir envolviendo cualquier cadena que quiera traducir en una etiqueta <translate>. Otros títulos y etiquetas también se encontrarán y se traducirán correctamente.

+

Configuraciones de Traducción de Docusaurus

+

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

+
npm run examples translations
+
+

o

+
yarn examples translations
+
+

Esto creará los siguientes archivos:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • El archivo pages/en/help-with-translations.js incluye la misma página de ayuda inicial generada por el script examples, pero ahora incluye etiquetas de traducción.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Traduciendo sus documentos existentes

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Habilitación de traducciones en páginas

+

Las páginas le permiten personalizar el diseño y el contenido específico de las páginas, como una página de índice personalizada o una página de ayuda.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Ajuste las cadenas que desee traducir en una etiqueta <translate> y agregue la siguiente instrucción require al principio del archivo:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

También puede incluir un atributo de descripción opcional para dar más contexto a un traductor sobre cómo traducir la cadena:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Reunir cadenas para traducir

+

Las cadenas dentro de las páginas localizadas se deben extraer y proporcionar a Crowdin.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

La ejecución del script generará un archivo website/i18n/en.json que contiene todas las cadenas que se traducirán del inglés a otros idiomas.

+

El script incluirá texto de los siguientes lugares:

+
    +
  • title y sidebar_label cadenas en los encabezados de documentos de markdown
    • +
  • nombres de categoría en sidebars.json
    • +
  • tagline en siteConfig.js
    • +
  • enlace de encabezado label cadenas en siteConfig.js
    • +
  • cadenas incluidas en la etiqueta <translate>etiquetas en cualquier archivo .js dentro de pages
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Cómo se traducen las cadenas

+

Docusaurus en sí no hace ninguna traducción de un idioma a otro. En cambio, integra Crowdin para cargar traducciones y luego descarga los archivos adecuadamente traducidos de Crowdin.

+

Cómo utiliza Docusaurus las cadenas de traducción

+

Esta sección proporciona un contexto sobre cómo funcionan las traducciones en Docusaurus.

+

Cadenas

+

Un sitio de Docusaurus tiene muchas cadenas usadas a lo largo de él que requieren localización. Sin embargo, mantener una lista de cadenas usadas en un sitio puede ser laborioso. Docusaurus simplifies this by centralizing strings.

+

La navegación del encabezado, por ejemplo, puede tener enlaces a 'Inicio' o a su 'Blog'. Esta y otras cadenas encontradas en los encabezados y barras laterales de las páginas se extraen y se colocan en i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Luego, cuando se generen las páginas en español, Docusaurus reemplazará la versión en inglés de las cadenas correspondientes con cadenas traducidas del archivo correspondiente de cadenas localizadas (por ejemplo, en un sitio habilitado en español, 'Ayuda' se convertirá en 'Ayuda').

+

Archivos de Markdown

+

Para los propios archivos de documentación, las versiones traducidas de estos archivos se descargan y luego se procesan a través de la plantilla de diseño adecuada.

+

Otras páginas

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Puede usar Crowdin's guides para obtener más información sobre el flujo de trabajo de las traducciones. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Sincronización manual de archivos

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Aquí hay un archivo de ejemplo circle.yml:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

El comando crowdin usa el archivo crowdin.yaml generado con el script examples. Debe colocarse en el directorio de su proyecto para configurar cómo y qué archivos se cargan/descargan.

+

Tenga en cuenta que en el archivo crowdin.yaml, CROWDIN_PROJECT_ID y CROWDIN_API_KEY se configuran las variables de entorno en Circle para su proyecto Crowdin. Se pueden encontrar en la configuración de tu proyecto Crowdin.

+

Ahora, Circle lo ayudará a obtener traducciones automáticamente antes de construir su sitio web. El archivo crowdin.yaml provisto copiará los documentos traducidos en website/translated_docs/, y las versiones traducidas del archivo i18n/en.json en i18n/${language}.json.

+

Si desea usar Crowdin en su máquina localmente, puede instalar la herramienta Crowdin CLI y ejecutar los mismos comandos que se encuentran en el archivo circle.yaml. La única diferencia es que debe establecer los valores project_identifier y api_key en el archivo crowdin.yaml, ya que no tendrá configuradas las variables de entorno Circle.

+

Versiones y Traducciones

+

Si desea tener traducción y versiones para su documentación, agregue la siguiente sección al final de su archivo crowdin.yaml:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Los documentos traducidos y versionados se copiarán en el sitio web website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/es-ES/versioning.html b/docs/es-ES/versioning.html new file mode 100644 index 0000000000..438aa41197 --- /dev/null +++ b/docs/es-ES/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/es-ES/versioning/index.html b/docs/es-ES/versioning/index.html new file mode 100644 index 0000000000..438aa41197 --- /dev/null +++ b/docs/es-ES/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Cómo crear nuevas versiones

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Patrones de versiones

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Almacenamiento de archivos para cada versión

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Funcionalidad de respaldo

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Cambiar el nombre de las versiones existentes

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versiones y Traducciones

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.11/api-pages.html b/docs/tr/1.0.11/api-pages.html new file mode 100644 index 0000000000..a6c9e8a195 --- /dev/null +++ b/docs/tr/1.0.11/api-pages.html @@ -0,0 +1,175 @@ +Pages and Styles · Docusaurus

1.0.11

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>[Markdown syntax for a link](http://www.example.com)</MarkdownBlock>
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...         
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"  
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p><translate>I like translations</translate></p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">Community</translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require("../../server/translate.js").translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.11/api-pages/index.html b/docs/tr/1.0.11/api-pages/index.html new file mode 100644 index 0000000000..a6c9e8a195 --- /dev/null +++ b/docs/tr/1.0.11/api-pages/index.html @@ -0,0 +1,175 @@ +Pages and Styles · Docusaurus

1.0.11

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>[Markdown syntax for a link](http://www.example.com)</MarkdownBlock>
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...         
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"  
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p><translate>I like translations</translate></p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">Community</translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require("../../server/translate.js").translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.11/blog.html b/docs/tr/1.0.11/blog.html new file mode 100644 index 0000000000..0e49407479 --- /dev/null +++ b/docs/tr/1.0.11/blog.html @@ -0,0 +1,129 @@ +Adding a Blog · Docusaurus

1.0.11

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipusm..
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The url associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook ID that is used to extract the profile picture.
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.11/blog/index.html b/docs/tr/1.0.11/blog/index.html new file mode 100644 index 0000000000..0e49407479 --- /dev/null +++ b/docs/tr/1.0.11/blog/index.html @@ -0,0 +1,129 @@ +Adding a Blog · Docusaurus

1.0.11

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipusm..
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The url associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook ID that is used to extract the profile picture.
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.11/commands.html b/docs/tr/1.0.11/commands.html new file mode 100644 index 0000000000..fdc50a7208 --- /dev/null +++ b/docs/tr/1.0.11/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.11

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.11/commands/index.html b/docs/tr/1.0.11/commands/index.html new file mode 100644 index 0000000000..fdc50a7208 --- /dev/null +++ b/docs/tr/1.0.11/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.11

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.11/custom-pages.html b/docs/tr/1.0.11/custom-pages.html new file mode 100644 index 0000000000..e84290e525 --- /dev/null +++ b/docs/tr/1.0.11/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.11

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.11/custom-pages/index.html b/docs/tr/1.0.11/custom-pages/index.html new file mode 100644 index 0000000000..e84290e525 --- /dev/null +++ b/docs/tr/1.0.11/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.11

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.11/doc-markdown.html b/docs/tr/1.0.11/doc-markdown.html new file mode 100644 index 0000000000..f08305b5cb --- /dev/null +++ b/docs/tr/1.0.11/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.11

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.11/doc-markdown/index.html b/docs/tr/1.0.11/doc-markdown/index.html new file mode 100644 index 0000000000..f08305b5cb --- /dev/null +++ b/docs/tr/1.0.11/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.11

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.11/installation.html b/docs/tr/1.0.11/installation.html new file mode 100644 index 0000000000..599c685a3e --- /dev/null +++ b/docs/tr/1.0.11/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.11

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Kurulumu doğrulama

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.11/installation/index.html b/docs/tr/1.0.11/installation/index.html new file mode 100644 index 0000000000..599c685a3e --- /dev/null +++ b/docs/tr/1.0.11/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.11

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Kurulumu doğrulama

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.11/navigation.html b/docs/tr/1.0.11/navigation.html new file mode 100644 index 0000000000..004e3bacb5 --- /dev/null +++ b/docs/tr/1.0.11/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.11

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.11/navigation/index.html b/docs/tr/1.0.11/navigation/index.html new file mode 100644 index 0000000000..004e3bacb5 --- /dev/null +++ b/docs/tr/1.0.11/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.11

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.11/publishing.html b/docs/tr/1.0.11/publishing.html new file mode 100644 index 0000000000..bdda0646f7 --- /dev/null +++ b/docs/tr/1.0.11/publishing.html @@ -0,0 +1,185 @@ +Publishing your site · Docusaurus

1.0.11

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's "html" directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+
    +
  • organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
    • +
  • projectName: The name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
    • +
+
+

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.

+

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:

+
    +
  • GIT_USER: The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
    • +
+

There are also two optional parameters that are set as environment variables:

+
    +

  • USE_SSH: If this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.

    • +

  • CURRENT_BRANCH: The branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.

    • +
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master   
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.11/publishing/index.html b/docs/tr/1.0.11/publishing/index.html new file mode 100644 index 0000000000..bdda0646f7 --- /dev/null +++ b/docs/tr/1.0.11/publishing/index.html @@ -0,0 +1,185 @@ +Publishing your site · Docusaurus

1.0.11

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's "html" directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+
    +
  • organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
    • +
  • projectName: The name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
    • +
+
+

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.

+

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:

+
    +
  • GIT_USER: The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
    • +
+

There are also two optional parameters that are set as environment variables:

+
    +

  • USE_SSH: If this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.

    • +

  • CURRENT_BRANCH: The branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.

    • +
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master   
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.11/search.html b/docs/tr/1.0.11/search.html new file mode 100644 index 0000000000..5f11130074 --- /dev/null +++ b/docs/tr/1.0.11/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.11

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.11/search/index.html b/docs/tr/1.0.11/search/index.html new file mode 100644 index 0000000000..5f11130074 --- /dev/null +++ b/docs/tr/1.0.11/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.11

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.11/site-config.html b/docs/tr/1.0.11/site-config.html new file mode 100644 index 0000000000..a87e41ade8 --- /dev/null +++ b/docs/tr/1.0.11/site-config.html @@ -0,0 +1,231 @@ +siteConfig.js · Docusaurus

1.0.11

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - url for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - url for an Open Graph image. This image will show up when your site is shared on Facebook, Twitter and any other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - url for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with all fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+// For github.io type URLS, you would combine the url and baseUrl like:
+// url: "https://reasonml.github.io",
+// baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+// For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+// users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true"
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.11/site-config/index.html b/docs/tr/1.0.11/site-config/index.html new file mode 100644 index 0000000000..a87e41ade8 --- /dev/null +++ b/docs/tr/1.0.11/site-config/index.html @@ -0,0 +1,231 @@ +siteConfig.js · Docusaurus

1.0.11

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - url for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - url for an Open Graph image. This image will show up when your site is shared on Facebook, Twitter and any other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - url for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with all fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+// For github.io type URLS, you would combine the url and baseUrl like:
+// url: "https://reasonml.github.io",
+// baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+// For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+// users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true"
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.11/site-creation.html b/docs/tr/1.0.11/site-creation.html new file mode 100644 index 0000000000..e79bb75ef8 --- /dev/null +++ b/docs/tr/1.0.11/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.11

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.11/site-creation/index.html b/docs/tr/1.0.11/site-creation/index.html new file mode 100644 index 0000000000..e79bb75ef8 --- /dev/null +++ b/docs/tr/1.0.11/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.11

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.11/site-preparation.html b/docs/tr/1.0.11/site-preparation.html new file mode 100644 index 0000000000..8ca0d19e9b --- /dev/null +++ b/docs/tr/1.0.11/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.11

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.11/site-preparation/index.html b/docs/tr/1.0.11/site-preparation/index.html new file mode 100644 index 0000000000..8ca0d19e9b --- /dev/null +++ b/docs/tr/1.0.11/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.11

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.11/translation.html b/docs/tr/1.0.11/translation.html new file mode 100644 index 0000000000..0ba408b07d --- /dev/null +++ b/docs/tr/1.0.11/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.11

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.11/translation/index.html b/docs/tr/1.0.11/translation/index.html new file mode 100644 index 0000000000..0ba408b07d --- /dev/null +++ b/docs/tr/1.0.11/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.11

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.11/versioning.html b/docs/tr/1.0.11/versioning.html new file mode 100644 index 0000000000..4b032cf46c --- /dev/null +++ b/docs/tr/1.0.11/versioning.html @@ -0,0 +1,108 @@ +Versioning · Docusaurus

1.0.11

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.11/versioning/index.html b/docs/tr/1.0.11/versioning/index.html new file mode 100644 index 0000000000..4b032cf46c --- /dev/null +++ b/docs/tr/1.0.11/versioning/index.html @@ -0,0 +1,108 @@ +Versioning · Docusaurus

1.0.11

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.12/api-pages.html b/docs/tr/1.0.12/api-pages.html new file mode 100644 index 0000000000..97cb78e155 --- /dev/null +++ b/docs/tr/1.0.12/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.12

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.12/api-pages/index.html b/docs/tr/1.0.12/api-pages/index.html new file mode 100644 index 0000000000..97cb78e155 --- /dev/null +++ b/docs/tr/1.0.12/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.12

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.12/blog.html b/docs/tr/1.0.12/blog.html new file mode 100644 index 0000000000..2b11de33ea --- /dev/null +++ b/docs/tr/1.0.12/blog.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.12

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.12/blog/index.html b/docs/tr/1.0.12/blog/index.html new file mode 100644 index 0000000000..2b11de33ea --- /dev/null +++ b/docs/tr/1.0.12/blog/index.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.12

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.12/commands.html b/docs/tr/1.0.12/commands.html new file mode 100644 index 0000000000..91e097806b --- /dev/null +++ b/docs/tr/1.0.12/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.12

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.12/commands/index.html b/docs/tr/1.0.12/commands/index.html new file mode 100644 index 0000000000..91e097806b --- /dev/null +++ b/docs/tr/1.0.12/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.12

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.12/custom-pages.html b/docs/tr/1.0.12/custom-pages.html new file mode 100644 index 0000000000..bf63d544e5 --- /dev/null +++ b/docs/tr/1.0.12/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.12

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.12/custom-pages/index.html b/docs/tr/1.0.12/custom-pages/index.html new file mode 100644 index 0000000000..bf63d544e5 --- /dev/null +++ b/docs/tr/1.0.12/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.12

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.12/doc-markdown.html b/docs/tr/1.0.12/doc-markdown.html new file mode 100644 index 0000000000..cb56c65b46 --- /dev/null +++ b/docs/tr/1.0.12/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.12

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.12/doc-markdown/index.html b/docs/tr/1.0.12/doc-markdown/index.html new file mode 100644 index 0000000000..cb56c65b46 --- /dev/null +++ b/docs/tr/1.0.12/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.12

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.12/installation.html b/docs/tr/1.0.12/installation.html new file mode 100644 index 0000000000..3b9983f2dd --- /dev/null +++ b/docs/tr/1.0.12/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.12

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Kurulumu doğrulama

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.12/installation/index.html b/docs/tr/1.0.12/installation/index.html new file mode 100644 index 0000000000..3b9983f2dd --- /dev/null +++ b/docs/tr/1.0.12/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.12

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Kurulumu doğrulama

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.12/navigation.html b/docs/tr/1.0.12/navigation.html new file mode 100644 index 0000000000..f1da42d0fe --- /dev/null +++ b/docs/tr/1.0.12/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.12

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.12/navigation/index.html b/docs/tr/1.0.12/navigation/index.html new file mode 100644 index 0000000000..f1da42d0fe --- /dev/null +++ b/docs/tr/1.0.12/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.12

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.12/publishing.html b/docs/tr/1.0.12/publishing.html new file mode 100644 index 0000000000..5c1ff3db95 --- /dev/null +++ b/docs/tr/1.0.12/publishing.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.12

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.12/publishing/index.html b/docs/tr/1.0.12/publishing/index.html new file mode 100644 index 0000000000..5c1ff3db95 --- /dev/null +++ b/docs/tr/1.0.12/publishing/index.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.12

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.12/search.html b/docs/tr/1.0.12/search.html new file mode 100644 index 0000000000..e9270cb236 --- /dev/null +++ b/docs/tr/1.0.12/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.12

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.12/search/index.html b/docs/tr/1.0.12/search/index.html new file mode 100644 index 0000000000..e9270cb236 --- /dev/null +++ b/docs/tr/1.0.12/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.12

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.12/site-config.html b/docs/tr/1.0.12/site-config.html new file mode 100644 index 0000000000..870621c940 --- /dev/null +++ b/docs/tr/1.0.12/site-config.html @@ -0,0 +1,234 @@ +siteConfig.js · Docusaurus

1.0.12

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.12/site-config/index.html b/docs/tr/1.0.12/site-config/index.html new file mode 100644 index 0000000000..870621c940 --- /dev/null +++ b/docs/tr/1.0.12/site-config/index.html @@ -0,0 +1,234 @@ +siteConfig.js · Docusaurus

1.0.12

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.12/site-creation.html b/docs/tr/1.0.12/site-creation.html new file mode 100644 index 0000000000..740bf3e468 --- /dev/null +++ b/docs/tr/1.0.12/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.12

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.12/site-creation/index.html b/docs/tr/1.0.12/site-creation/index.html new file mode 100644 index 0000000000..740bf3e468 --- /dev/null +++ b/docs/tr/1.0.12/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.12

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.12/site-preparation.html b/docs/tr/1.0.12/site-preparation.html new file mode 100644 index 0000000000..85eae21c1a --- /dev/null +++ b/docs/tr/1.0.12/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.12

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.12/site-preparation/index.html b/docs/tr/1.0.12/site-preparation/index.html new file mode 100644 index 0000000000..85eae21c1a --- /dev/null +++ b/docs/tr/1.0.12/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.12

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.12/translation.html b/docs/tr/1.0.12/translation.html new file mode 100644 index 0000000000..c1c1b246a9 --- /dev/null +++ b/docs/tr/1.0.12/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.12

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.12/translation/index.html b/docs/tr/1.0.12/translation/index.html new file mode 100644 index 0000000000..c1c1b246a9 --- /dev/null +++ b/docs/tr/1.0.12/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.12

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.12/versioning.html b/docs/tr/1.0.12/versioning.html new file mode 100644 index 0000000000..d3dd306ab3 --- /dev/null +++ b/docs/tr/1.0.12/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.12

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.12/versioning/index.html b/docs/tr/1.0.12/versioning/index.html new file mode 100644 index 0000000000..d3dd306ab3 --- /dev/null +++ b/docs/tr/1.0.12/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.12

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.13/api-pages.html b/docs/tr/1.0.13/api-pages.html new file mode 100644 index 0000000000..779cae3c3c --- /dev/null +++ b/docs/tr/1.0.13/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.13

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.13/api-pages/index.html b/docs/tr/1.0.13/api-pages/index.html new file mode 100644 index 0000000000..779cae3c3c --- /dev/null +++ b/docs/tr/1.0.13/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.13

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.13/blog.html b/docs/tr/1.0.13/blog.html new file mode 100644 index 0000000000..ae2de5107a --- /dev/null +++ b/docs/tr/1.0.13/blog.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.13

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.13/blog/index.html b/docs/tr/1.0.13/blog/index.html new file mode 100644 index 0000000000..ae2de5107a --- /dev/null +++ b/docs/tr/1.0.13/blog/index.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.13

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.13/commands.html b/docs/tr/1.0.13/commands.html new file mode 100644 index 0000000000..203d21f1b9 --- /dev/null +++ b/docs/tr/1.0.13/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.13

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.13/commands/index.html b/docs/tr/1.0.13/commands/index.html new file mode 100644 index 0000000000..203d21f1b9 --- /dev/null +++ b/docs/tr/1.0.13/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.13

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.13/custom-pages.html b/docs/tr/1.0.13/custom-pages.html new file mode 100644 index 0000000000..937173d89d --- /dev/null +++ b/docs/tr/1.0.13/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.13

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.13/custom-pages/index.html b/docs/tr/1.0.13/custom-pages/index.html new file mode 100644 index 0000000000..937173d89d --- /dev/null +++ b/docs/tr/1.0.13/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.13

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.13/doc-markdown.html b/docs/tr/1.0.13/doc-markdown.html new file mode 100644 index 0000000000..366ab3b1a1 --- /dev/null +++ b/docs/tr/1.0.13/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.13

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.13/doc-markdown/index.html b/docs/tr/1.0.13/doc-markdown/index.html new file mode 100644 index 0000000000..366ab3b1a1 --- /dev/null +++ b/docs/tr/1.0.13/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.13

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.13/installation.html b/docs/tr/1.0.13/installation.html new file mode 100644 index 0000000000..15aa146be6 --- /dev/null +++ b/docs/tr/1.0.13/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.13

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Kurulumu doğrulama

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.13/installation/index.html b/docs/tr/1.0.13/installation/index.html new file mode 100644 index 0000000000..15aa146be6 --- /dev/null +++ b/docs/tr/1.0.13/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.13

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

Kurulumu doğrulama

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.13/navigation.html b/docs/tr/1.0.13/navigation.html new file mode 100644 index 0000000000..539a6ba469 --- /dev/null +++ b/docs/tr/1.0.13/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.13

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.13/navigation/index.html b/docs/tr/1.0.13/navigation/index.html new file mode 100644 index 0000000000..539a6ba469 --- /dev/null +++ b/docs/tr/1.0.13/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.13

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.13/publishing.html b/docs/tr/1.0.13/publishing.html new file mode 100644 index 0000000000..665167370c --- /dev/null +++ b/docs/tr/1.0.13/publishing.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.13

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.13/publishing/index.html b/docs/tr/1.0.13/publishing/index.html new file mode 100644 index 0000000000..665167370c --- /dev/null +++ b/docs/tr/1.0.13/publishing/index.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.13

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.13/search.html b/docs/tr/1.0.13/search.html new file mode 100644 index 0000000000..115999b81c --- /dev/null +++ b/docs/tr/1.0.13/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.13

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.13/search/index.html b/docs/tr/1.0.13/search/index.html new file mode 100644 index 0000000000..115999b81c --- /dev/null +++ b/docs/tr/1.0.13/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.13

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.13/site-config.html b/docs/tr/1.0.13/site-config.html new file mode 100644 index 0000000000..d77420f512 --- /dev/null +++ b/docs/tr/1.0.13/site-config.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.13

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.13/site-config/index.html b/docs/tr/1.0.13/site-config/index.html new file mode 100644 index 0000000000..d77420f512 --- /dev/null +++ b/docs/tr/1.0.13/site-config/index.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.13

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.13/site-creation.html b/docs/tr/1.0.13/site-creation.html new file mode 100644 index 0000000000..f38252dd9e --- /dev/null +++ b/docs/tr/1.0.13/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.13

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.13/site-creation/index.html b/docs/tr/1.0.13/site-creation/index.html new file mode 100644 index 0000000000..f38252dd9e --- /dev/null +++ b/docs/tr/1.0.13/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.13

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.13/site-preparation.html b/docs/tr/1.0.13/site-preparation.html new file mode 100644 index 0000000000..9a2b0e2861 --- /dev/null +++ b/docs/tr/1.0.13/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.13

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.13/site-preparation/index.html b/docs/tr/1.0.13/site-preparation/index.html new file mode 100644 index 0000000000..9a2b0e2861 --- /dev/null +++ b/docs/tr/1.0.13/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.13

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.13/translation.html b/docs/tr/1.0.13/translation.html new file mode 100644 index 0000000000..ab12dcaad2 --- /dev/null +++ b/docs/tr/1.0.13/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.13

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.13/translation/index.html b/docs/tr/1.0.13/translation/index.html new file mode 100644 index 0000000000..ab12dcaad2 --- /dev/null +++ b/docs/tr/1.0.13/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.13

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.13/versioning.html b/docs/tr/1.0.13/versioning.html new file mode 100644 index 0000000000..520e50bf4a --- /dev/null +++ b/docs/tr/1.0.13/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.13

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.13/versioning/index.html b/docs/tr/1.0.13/versioning/index.html new file mode 100644 index 0000000000..520e50bf4a --- /dev/null +++ b/docs/tr/1.0.13/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.13

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.14/api-pages.html b/docs/tr/1.0.14/api-pages.html new file mode 100644 index 0000000000..2c63ead85b --- /dev/null +++ b/docs/tr/1.0.14/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.14

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.14/api-pages/index.html b/docs/tr/1.0.14/api-pages/index.html new file mode 100644 index 0000000000..2c63ead85b --- /dev/null +++ b/docs/tr/1.0.14/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.14

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

Urls for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.14/blog.html b/docs/tr/1.0.14/blog.html new file mode 100644 index 0000000000..4eeb136962 --- /dev/null +++ b/docs/tr/1.0.14/blog.html @@ -0,0 +1,191 @@ +Adding a Blog · Docusaurus

1.0.14

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. +

    + Create a file index.html in website/static/. +

    +
    2. +
    <li>
+  <p>
+    Place the contents of the template below into <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Delete the dynamic landing page <code>website/pages/en/index.js</code>
+  </p>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+

+ 

<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=blog/">
+        <script type="text/javascript">
+            window.location.href = "blog/"
+        </script>
+        <title>Title of Your Blog</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='blog/'>link</a>.
+    </body>
+</html>
+

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.14/blog/index.html b/docs/tr/1.0.14/blog/index.html new file mode 100644 index 0000000000..4eeb136962 --- /dev/null +++ b/docs/tr/1.0.14/blog/index.html @@ -0,0 +1,191 @@ +Adding a Blog · Docusaurus

1.0.14

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. +

    + Create a file index.html in website/static/. +

    +
    2. +
    <li>
+  <p>
+    Place the contents of the template below into <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Delete the dynamic landing page <code>website/pages/en/index.js</code>
+  </p>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+

+ 

<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=blog/">
+        <script type="text/javascript">
+            window.location.href = "blog/"
+        </script>
+        <title>Title of Your Blog</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='blog/'>link</a>.
+    </body>
+</html>
+

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.14/commands.html b/docs/tr/1.0.14/commands.html new file mode 100644 index 0000000000..36181a7767 --- /dev/null +++ b/docs/tr/1.0.14/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.14

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.14/commands/index.html b/docs/tr/1.0.14/commands/index.html new file mode 100644 index 0000000000..36181a7767 --- /dev/null +++ b/docs/tr/1.0.14/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.14

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.14/custom-pages.html b/docs/tr/1.0.14/custom-pages.html new file mode 100644 index 0000000000..adffa6f700 --- /dev/null +++ b/docs/tr/1.0.14/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.14

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.14/custom-pages/index.html b/docs/tr/1.0.14/custom-pages/index.html new file mode 100644 index 0000000000..adffa6f700 --- /dev/null +++ b/docs/tr/1.0.14/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.14

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.14/doc-markdown.html b/docs/tr/1.0.14/doc-markdown.html new file mode 100644 index 0000000000..510d2275ad --- /dev/null +++ b/docs/tr/1.0.14/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.14

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.14/doc-markdown/index.html b/docs/tr/1.0.14/doc-markdown/index.html new file mode 100644 index 0000000000..510d2275ad --- /dev/null +++ b/docs/tr/1.0.14/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.14

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.14/installation.html b/docs/tr/1.0.14/installation.html new file mode 100644 index 0000000000..dc44c1c757 --- /dev/null +++ b/docs/tr/1.0.14/installation.html @@ -0,0 +1,106 @@ +Installation · Docusaurus

1.0.14

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init > If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    4. +
+
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.14/installation/index.html b/docs/tr/1.0.14/installation/index.html new file mode 100644 index 0000000000..dc44c1c757 --- /dev/null +++ b/docs/tr/1.0.14/installation/index.html @@ -0,0 +1,106 @@ +Installation · Docusaurus

1.0.14

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init > If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    4. +
+
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.14/navigation.html b/docs/tr/1.0.14/navigation.html new file mode 100644 index 0000000000..caf1b3cef7 --- /dev/null +++ b/docs/tr/1.0.14/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.14

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.14/navigation/index.html b/docs/tr/1.0.14/navigation/index.html new file mode 100644 index 0000000000..caf1b3cef7 --- /dev/null +++ b/docs/tr/1.0.14/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.14

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.14/publishing.html b/docs/tr/1.0.14/publishing.html new file mode 100644 index 0000000000..6fddfbe589 --- /dev/null +++ b/docs/tr/1.0.14/publishing.html @@ -0,0 +1,221 @@ +Publishing your site · Docusaurus

1.0.14

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +
  1. Select New site from Git
    2. +
  2. Connect to your preferred Git provider.
    3. +
  3. Select the branch to deploy. Default is master
    4. +
  4. Configure your build steps:
    5. +
+
    +
  • For your build command enter: cd website; npm install; npm run build;
    • +
  • For publish directory: build/<projectName> (use the projectName from your siteConfig)
    • +
+
    +
  1. Click Deploy site
    2. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.14/publishing/index.html b/docs/tr/1.0.14/publishing/index.html new file mode 100644 index 0000000000..6fddfbe589 --- /dev/null +++ b/docs/tr/1.0.14/publishing/index.html @@ -0,0 +1,221 @@ +Publishing your site · Docusaurus

1.0.14

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +
  1. Select New site from Git
    2. +
  2. Connect to your preferred Git provider.
    3. +
  3. Select the branch to deploy. Default is master
    4. +
  4. Configure your build steps:
    5. +
+
    +
  • For your build command enter: cd website; npm install; npm run build;
    • +
  • For publish directory: build/<projectName> (use the projectName from your siteConfig)
    • +
+
    +
  1. Click Deploy site
    2. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.14/search.html b/docs/tr/1.0.14/search.html new file mode 100644 index 0000000000..5850fdbee8 --- /dev/null +++ b/docs/tr/1.0.14/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.14

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.14/search/index.html b/docs/tr/1.0.14/search/index.html new file mode 100644 index 0000000000..5850fdbee8 --- /dev/null +++ b/docs/tr/1.0.14/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.14

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

Arama Çubuğunu Etkinleştirme

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.14/site-config.html b/docs/tr/1.0.14/site-config.html new file mode 100644 index 0000000000..ba63f2e3b8 --- /dev/null +++ b/docs/tr/1.0.14/site-config.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.14

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.14/site-config/index.html b/docs/tr/1.0.14/site-config/index.html new file mode 100644 index 0000000000..ba63f2e3b8 --- /dev/null +++ b/docs/tr/1.0.14/site-config/index.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.14

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.14/site-creation.html b/docs/tr/1.0.14/site-creation.html new file mode 100644 index 0000000000..853b5a26dc --- /dev/null +++ b/docs/tr/1.0.14/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.14

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+        <script type="text/javascript">
+            window.location.href = "docs/id-of-doc-to-land-on.html"
+        </script>
+        <title>Your Site Title Here</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='docs/id-of-doc-to-land-on.html'>link</a>.
+    </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.14/site-creation/index.html b/docs/tr/1.0.14/site-creation/index.html new file mode 100644 index 0000000000..853b5a26dc --- /dev/null +++ b/docs/tr/1.0.14/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.14

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+        <script type="text/javascript">
+            window.location.href = "docs/id-of-doc-to-land-on.html"
+        </script>
+        <title>Your Site Title Here</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='docs/id-of-doc-to-land-on.html'>link</a>.
+    </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.14/site-preparation.html b/docs/tr/1.0.14/site-preparation.html new file mode 100644 index 0000000000..ff2cc8eb43 --- /dev/null +++ b/docs/tr/1.0.14/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.14

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.14/site-preparation/index.html b/docs/tr/1.0.14/site-preparation/index.html new file mode 100644 index 0000000000..ff2cc8eb43 --- /dev/null +++ b/docs/tr/1.0.14/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.14

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.14/translation.html b/docs/tr/1.0.14/translation.html new file mode 100644 index 0000000000..02a7f31d8b --- /dev/null +++ b/docs/tr/1.0.14/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.14

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.14/translation/index.html b/docs/tr/1.0.14/translation/index.html new file mode 100644 index 0000000000..02a7f31d8b --- /dev/null +++ b/docs/tr/1.0.14/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.14

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.14/versioning.html b/docs/tr/1.0.14/versioning.html new file mode 100644 index 0000000000..2b2c38d407 --- /dev/null +++ b/docs/tr/1.0.14/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.14

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.14/versioning/index.html b/docs/tr/1.0.14/versioning/index.html new file mode 100644 index 0000000000..2b2c38d407 --- /dev/null +++ b/docs/tr/1.0.14/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.14

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.15/api-pages.html b/docs/tr/1.0.15/api-pages.html new file mode 100644 index 0000000000..fc21155f86 --- /dev/null +++ b/docs/tr/1.0.15/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.15

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.15/api-pages/index.html b/docs/tr/1.0.15/api-pages/index.html new file mode 100644 index 0000000000..fc21155f86 --- /dev/null +++ b/docs/tr/1.0.15/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.15

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.0.15/blog.html b/docs/tr/1.0.15/blog.html new file mode 100644 index 0000000000..6582013296 --- /dev/null +++ b/docs/tr/1.0.15/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.0.15

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.15/blog/index.html b/docs/tr/1.0.15/blog/index.html new file mode 100644 index 0000000000..6582013296 --- /dev/null +++ b/docs/tr/1.0.15/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.0.15

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.0.15/commands.html b/docs/tr/1.0.15/commands.html new file mode 100644 index 0000000000..d1704d3ab2 --- /dev/null +++ b/docs/tr/1.0.15/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.15

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.15/commands/index.html b/docs/tr/1.0.15/commands/index.html new file mode 100644 index 0000000000..d1704d3ab2 --- /dev/null +++ b/docs/tr/1.0.15/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.15

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

Eşdeğeri: -c

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.0.15/custom-pages.html b/docs/tr/1.0.15/custom-pages.html new file mode 100644 index 0000000000..1cc1a98575 --- /dev/null +++ b/docs/tr/1.0.15/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.15

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.15/custom-pages/index.html b/docs/tr/1.0.15/custom-pages/index.html new file mode 100644 index 0000000000..1cc1a98575 --- /dev/null +++ b/docs/tr/1.0.15/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.15

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.0.15/doc-markdown.html b/docs/tr/1.0.15/doc-markdown.html new file mode 100644 index 0000000000..dc500f2575 --- /dev/null +++ b/docs/tr/1.0.15/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.0.15

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.15/doc-markdown/index.html b/docs/tr/1.0.15/doc-markdown/index.html new file mode 100644 index 0000000000..dc500f2575 --- /dev/null +++ b/docs/tr/1.0.15/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.0.15

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.0.15/installation.html b/docs/tr/1.0.15/installation.html new file mode 100644 index 0000000000..96ecf81ee8 --- /dev/null +++ b/docs/tr/1.0.15/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.0.15

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.15/installation/index.html b/docs/tr/1.0.15/installation/index.html new file mode 100644 index 0000000000..96ecf81ee8 --- /dev/null +++ b/docs/tr/1.0.15/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.0.15

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.0.15/navigation.html b/docs/tr/1.0.15/navigation.html new file mode 100644 index 0000000000..33b2e68a89 --- /dev/null +++ b/docs/tr/1.0.15/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.0.15

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.15/navigation/index.html b/docs/tr/1.0.15/navigation/index.html new file mode 100644 index 0000000000..33b2e68a89 --- /dev/null +++ b/docs/tr/1.0.15/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.0.15

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.0.15/publishing.html b/docs/tr/1.0.15/publishing.html new file mode 100644 index 0000000000..1d4b501ace --- /dev/null +++ b/docs/tr/1.0.15/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.0.15

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.15/publishing/index.html b/docs/tr/1.0.15/publishing/index.html new file mode 100644 index 0000000000..1d4b501ace --- /dev/null +++ b/docs/tr/1.0.15/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.0.15

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.0.15/search.html b/docs/tr/1.0.15/search.html new file mode 100644 index 0000000000..32e27c6f0b --- /dev/null +++ b/docs/tr/1.0.15/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.0.15

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.15/search/index.html b/docs/tr/1.0.15/search/index.html new file mode 100644 index 0000000000..32e27c6f0b --- /dev/null +++ b/docs/tr/1.0.15/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.0.15

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.0.15/site-config.html b/docs/tr/1.0.15/site-config.html new file mode 100644 index 0000000000..8641abed0a --- /dev/null +++ b/docs/tr/1.0.15/site-config.html @@ -0,0 +1,239 @@ +siteConfig.js · Docusaurus

1.0.15

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site'
+
+
customDocsPath: 'website-docs'
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: 'doc1', label: 'Docs' },
+    { page: 'help', label: 'Help' },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B'
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink:
+    'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey:
+      '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github'
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ 'https://docusaurus.io/slash.js' ],
+  stylesheets: [ 'https://docusaurus.io/style.css' ],
+  facebookAppId: '1615782811974223',
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.15/site-config/index.html b/docs/tr/1.0.15/site-config/index.html new file mode 100644 index 0000000000..8641abed0a --- /dev/null +++ b/docs/tr/1.0.15/site-config/index.html @@ -0,0 +1,239 @@ +siteConfig.js · Docusaurus

1.0.15

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site'
+
+
customDocsPath: 'website-docs'
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: 'doc1', label: 'Docs' },
+    { page: 'help', label: 'Help' },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B'
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink:
+    'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey:
+      '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github'
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ 'https://docusaurus.io/slash.js' ],
+  stylesheets: [ 'https://docusaurus.io/style.css' ],
+  facebookAppId: '1615782811974223',
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.0.15/site-creation.html b/docs/tr/1.0.15/site-creation.html new file mode 100644 index 0000000000..bf887531be --- /dev/null +++ b/docs/tr/1.0.15/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.15

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.15/site-creation/index.html b/docs/tr/1.0.15/site-creation/index.html new file mode 100644 index 0000000000..bf887531be --- /dev/null +++ b/docs/tr/1.0.15/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.15

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.0.15/site-preparation.html b/docs/tr/1.0.15/site-preparation.html new file mode 100644 index 0000000000..210d541cc7 --- /dev/null +++ b/docs/tr/1.0.15/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.15

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.15/site-preparation/index.html b/docs/tr/1.0.15/site-preparation/index.html new file mode 100644 index 0000000000..210d541cc7 --- /dev/null +++ b/docs/tr/1.0.15/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.15

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.0.15/translation.html b/docs/tr/1.0.15/translation.html new file mode 100644 index 0000000000..9beafe3030 --- /dev/null +++ b/docs/tr/1.0.15/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.0.15

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.15/translation/index.html b/docs/tr/1.0.15/translation/index.html new file mode 100644 index 0000000000..9beafe3030 --- /dev/null +++ b/docs/tr/1.0.15/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.0.15

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.0.15/versioning.html b/docs/tr/1.0.15/versioning.html new file mode 100644 index 0000000000..a8dd10d4c1 --- /dev/null +++ b/docs/tr/1.0.15/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.15

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.0.15/versioning/index.html b/docs/tr/1.0.15/versioning/index.html new file mode 100644 index 0000000000..a8dd10d4c1 --- /dev/null +++ b/docs/tr/1.0.15/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.15

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.0/api-pages.html b/docs/tr/1.1.0/api-pages.html new file mode 100644 index 0000000000..f6cdc49c51 --- /dev/null +++ b/docs/tr/1.1.0/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.0

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.0/api-pages/index.html b/docs/tr/1.1.0/api-pages/index.html new file mode 100644 index 0000000000..f6cdc49c51 --- /dev/null +++ b/docs/tr/1.1.0/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.0

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.0/blog.html b/docs/tr/1.1.0/blog.html new file mode 100644 index 0000000000..00dc70509e --- /dev/null +++ b/docs/tr/1.1.0/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.0

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.0/blog/index.html b/docs/tr/1.1.0/blog/index.html new file mode 100644 index 0000000000..00dc70509e --- /dev/null +++ b/docs/tr/1.1.0/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.0

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.0/commands.html b/docs/tr/1.1.0/commands.html new file mode 100644 index 0000000000..946100a9bf --- /dev/null +++ b/docs/tr/1.1.0/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.0

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.0/commands/index.html b/docs/tr/1.1.0/commands/index.html new file mode 100644 index 0000000000..946100a9bf --- /dev/null +++ b/docs/tr/1.1.0/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.0

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.0/custom-pages.html b/docs/tr/1.1.0/custom-pages.html new file mode 100644 index 0000000000..0f4f5d642b --- /dev/null +++ b/docs/tr/1.1.0/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.0/custom-pages/index.html b/docs/tr/1.1.0/custom-pages/index.html new file mode 100644 index 0000000000..0f4f5d642b --- /dev/null +++ b/docs/tr/1.1.0/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.0/doc-markdown.html b/docs/tr/1.1.0/doc-markdown.html new file mode 100644 index 0000000000..3a2a51823b --- /dev/null +++ b/docs/tr/1.1.0/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.0

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.0/doc-markdown/index.html b/docs/tr/1.1.0/doc-markdown/index.html new file mode 100644 index 0000000000..3a2a51823b --- /dev/null +++ b/docs/tr/1.1.0/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.0

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.0/installation.html b/docs/tr/1.1.0/installation.html new file mode 100644 index 0000000000..3baabe928d --- /dev/null +++ b/docs/tr/1.1.0/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.0/installation/index.html b/docs/tr/1.1.0/installation/index.html new file mode 100644 index 0000000000..3baabe928d --- /dev/null +++ b/docs/tr/1.1.0/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.0/navigation.html b/docs/tr/1.1.0/navigation.html new file mode 100644 index 0000000000..534842eace --- /dev/null +++ b/docs/tr/1.1.0/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.0/navigation/index.html b/docs/tr/1.1.0/navigation/index.html new file mode 100644 index 0000000000..534842eace --- /dev/null +++ b/docs/tr/1.1.0/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.0/publishing.html b/docs/tr/1.1.0/publishing.html new file mode 100644 index 0000000000..13627c2aa8 --- /dev/null +++ b/docs/tr/1.1.0/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.0/publishing/index.html b/docs/tr/1.1.0/publishing/index.html new file mode 100644 index 0000000000..13627c2aa8 --- /dev/null +++ b/docs/tr/1.1.0/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.0/search.html b/docs/tr/1.1.0/search.html new file mode 100644 index 0000000000..1d87a33182 --- /dev/null +++ b/docs/tr/1.1.0/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.0

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.0/search/index.html b/docs/tr/1.1.0/search/index.html new file mode 100644 index 0000000000..1d87a33182 --- /dev/null +++ b/docs/tr/1.1.0/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.0

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.0/site-config.html b/docs/tr/1.1.0/site-config.html new file mode 100644 index 0000000000..8e4e17ea9c --- /dev/null +++ b/docs/tr/1.1.0/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.0

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.0/site-config/index.html b/docs/tr/1.1.0/site-config/index.html new file mode 100644 index 0000000000..8e4e17ea9c --- /dev/null +++ b/docs/tr/1.1.0/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.0

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.0/site-creation.html b/docs/tr/1.1.0/site-creation.html new file mode 100644 index 0000000000..22ba1a3371 --- /dev/null +++ b/docs/tr/1.1.0/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.0/site-creation/index.html b/docs/tr/1.1.0/site-creation/index.html new file mode 100644 index 0000000000..22ba1a3371 --- /dev/null +++ b/docs/tr/1.1.0/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.0/site-preparation.html b/docs/tr/1.1.0/site-preparation.html new file mode 100644 index 0000000000..aaf3c9d9cb --- /dev/null +++ b/docs/tr/1.1.0/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.0/site-preparation/index.html b/docs/tr/1.1.0/site-preparation/index.html new file mode 100644 index 0000000000..aaf3c9d9cb --- /dev/null +++ b/docs/tr/1.1.0/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.0/translation.html b/docs/tr/1.1.0/translation.html new file mode 100644 index 0000000000..93fd752703 --- /dev/null +++ b/docs/tr/1.1.0/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.0/translation/index.html b/docs/tr/1.1.0/translation/index.html new file mode 100644 index 0000000000..93fd752703 --- /dev/null +++ b/docs/tr/1.1.0/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.0/versioning.html b/docs/tr/1.1.0/versioning.html new file mode 100644 index 0000000000..cd1e78ae47 --- /dev/null +++ b/docs/tr/1.1.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.0/versioning/index.html b/docs/tr/1.1.0/versioning/index.html new file mode 100644 index 0000000000..cd1e78ae47 --- /dev/null +++ b/docs/tr/1.1.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.1/api-pages.html b/docs/tr/1.1.1/api-pages.html new file mode 100644 index 0000000000..8fd82e4573 --- /dev/null +++ b/docs/tr/1.1.1/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.1

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.1/api-pages/index.html b/docs/tr/1.1.1/api-pages/index.html new file mode 100644 index 0000000000..8fd82e4573 --- /dev/null +++ b/docs/tr/1.1.1/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.1

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.1/blog.html b/docs/tr/1.1.1/blog.html new file mode 100644 index 0000000000..4d868be5ef --- /dev/null +++ b/docs/tr/1.1.1/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.1

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.1/blog/index.html b/docs/tr/1.1.1/blog/index.html new file mode 100644 index 0000000000..4d868be5ef --- /dev/null +++ b/docs/tr/1.1.1/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.1

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.1/commands.html b/docs/tr/1.1.1/commands.html new file mode 100644 index 0000000000..aceaca3529 --- /dev/null +++ b/docs/tr/1.1.1/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.1

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.1/commands/index.html b/docs/tr/1.1.1/commands/index.html new file mode 100644 index 0000000000..aceaca3529 --- /dev/null +++ b/docs/tr/1.1.1/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.1

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.1/custom-pages.html b/docs/tr/1.1.1/custom-pages.html new file mode 100644 index 0000000000..848ec2a9fa --- /dev/null +++ b/docs/tr/1.1.1/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.1/custom-pages/index.html b/docs/tr/1.1.1/custom-pages/index.html new file mode 100644 index 0000000000..848ec2a9fa --- /dev/null +++ b/docs/tr/1.1.1/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.1/doc-markdown.html b/docs/tr/1.1.1/doc-markdown.html new file mode 100644 index 0000000000..ec877dab8d --- /dev/null +++ b/docs/tr/1.1.1/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.1

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.1/doc-markdown/index.html b/docs/tr/1.1.1/doc-markdown/index.html new file mode 100644 index 0000000000..ec877dab8d --- /dev/null +++ b/docs/tr/1.1.1/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.1

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.1/installation.html b/docs/tr/1.1.1/installation.html new file mode 100644 index 0000000000..adec7c06f2 --- /dev/null +++ b/docs/tr/1.1.1/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.1/installation/index.html b/docs/tr/1.1.1/installation/index.html new file mode 100644 index 0000000000..adec7c06f2 --- /dev/null +++ b/docs/tr/1.1.1/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.1/navigation.html b/docs/tr/1.1.1/navigation.html new file mode 100644 index 0000000000..59887ebdcb --- /dev/null +++ b/docs/tr/1.1.1/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.1/navigation/index.html b/docs/tr/1.1.1/navigation/index.html new file mode 100644 index 0000000000..59887ebdcb --- /dev/null +++ b/docs/tr/1.1.1/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.1/publishing.html b/docs/tr/1.1.1/publishing.html new file mode 100644 index 0000000000..84e1d3e9bc --- /dev/null +++ b/docs/tr/1.1.1/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.1/publishing/index.html b/docs/tr/1.1.1/publishing/index.html new file mode 100644 index 0000000000..84e1d3e9bc --- /dev/null +++ b/docs/tr/1.1.1/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.1/search.html b/docs/tr/1.1.1/search.html new file mode 100644 index 0000000000..00be0c5117 --- /dev/null +++ b/docs/tr/1.1.1/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.1

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.1/search/index.html b/docs/tr/1.1.1/search/index.html new file mode 100644 index 0000000000..00be0c5117 --- /dev/null +++ b/docs/tr/1.1.1/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.1

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.1/site-config.html b/docs/tr/1.1.1/site-config.html new file mode 100644 index 0000000000..46d4cab05d --- /dev/null +++ b/docs/tr/1.1.1/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.1

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.1/site-config/index.html b/docs/tr/1.1.1/site-config/index.html new file mode 100644 index 0000000000..46d4cab05d --- /dev/null +++ b/docs/tr/1.1.1/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.1

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.1/site-creation.html b/docs/tr/1.1.1/site-creation.html new file mode 100644 index 0000000000..c3ccac3f8f --- /dev/null +++ b/docs/tr/1.1.1/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.1/site-creation/index.html b/docs/tr/1.1.1/site-creation/index.html new file mode 100644 index 0000000000..c3ccac3f8f --- /dev/null +++ b/docs/tr/1.1.1/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.1/site-preparation.html b/docs/tr/1.1.1/site-preparation.html new file mode 100644 index 0000000000..46a9cd26e4 --- /dev/null +++ b/docs/tr/1.1.1/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.1/site-preparation/index.html b/docs/tr/1.1.1/site-preparation/index.html new file mode 100644 index 0000000000..46a9cd26e4 --- /dev/null +++ b/docs/tr/1.1.1/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.1/translation.html b/docs/tr/1.1.1/translation.html new file mode 100644 index 0000000000..c9d353ea11 --- /dev/null +++ b/docs/tr/1.1.1/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.1/translation/index.html b/docs/tr/1.1.1/translation/index.html new file mode 100644 index 0000000000..c9d353ea11 --- /dev/null +++ b/docs/tr/1.1.1/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.1/versioning.html b/docs/tr/1.1.1/versioning.html new file mode 100644 index 0000000000..398b83f29f --- /dev/null +++ b/docs/tr/1.1.1/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.1/versioning/index.html b/docs/tr/1.1.1/versioning/index.html new file mode 100644 index 0000000000..398b83f29f --- /dev/null +++ b/docs/tr/1.1.1/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.2/api-pages.html b/docs/tr/1.1.2/api-pages.html new file mode 100644 index 0000000000..574132795c --- /dev/null +++ b/docs/tr/1.1.2/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.2

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.2/api-pages/index.html b/docs/tr/1.1.2/api-pages/index.html new file mode 100644 index 0000000000..574132795c --- /dev/null +++ b/docs/tr/1.1.2/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.2

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.2/blog.html b/docs/tr/1.1.2/blog.html new file mode 100644 index 0000000000..1fe410d1b5 --- /dev/null +++ b/docs/tr/1.1.2/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.2

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.2/blog/index.html b/docs/tr/1.1.2/blog/index.html new file mode 100644 index 0000000000..1fe410d1b5 --- /dev/null +++ b/docs/tr/1.1.2/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.2

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.2/commands.html b/docs/tr/1.1.2/commands.html new file mode 100644 index 0000000000..98d5be49d4 --- /dev/null +++ b/docs/tr/1.1.2/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.2

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.2/commands/index.html b/docs/tr/1.1.2/commands/index.html new file mode 100644 index 0000000000..98d5be49d4 --- /dev/null +++ b/docs/tr/1.1.2/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.2

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.2/custom-pages.html b/docs/tr/1.1.2/custom-pages.html new file mode 100644 index 0000000000..c38c9c20da --- /dev/null +++ b/docs/tr/1.1.2/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.2

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.2/custom-pages/index.html b/docs/tr/1.1.2/custom-pages/index.html new file mode 100644 index 0000000000..c38c9c20da --- /dev/null +++ b/docs/tr/1.1.2/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.2

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.2/doc-markdown.html b/docs/tr/1.1.2/doc-markdown.html new file mode 100644 index 0000000000..cea4c23a79 --- /dev/null +++ b/docs/tr/1.1.2/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.2

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.2/doc-markdown/index.html b/docs/tr/1.1.2/doc-markdown/index.html new file mode 100644 index 0000000000..cea4c23a79 --- /dev/null +++ b/docs/tr/1.1.2/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.2

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.2/installation.html b/docs/tr/1.1.2/installation.html new file mode 100644 index 0000000000..221305f36d --- /dev/null +++ b/docs/tr/1.1.2/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.2

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.2/installation/index.html b/docs/tr/1.1.2/installation/index.html new file mode 100644 index 0000000000..221305f36d --- /dev/null +++ b/docs/tr/1.1.2/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.2

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.2/navigation.html b/docs/tr/1.1.2/navigation.html new file mode 100644 index 0000000000..e1fc1d35cd --- /dev/null +++ b/docs/tr/1.1.2/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.2

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.2/navigation/index.html b/docs/tr/1.1.2/navigation/index.html new file mode 100644 index 0000000000..e1fc1d35cd --- /dev/null +++ b/docs/tr/1.1.2/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.2

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.2/publishing.html b/docs/tr/1.1.2/publishing.html new file mode 100644 index 0000000000..81abbb718f --- /dev/null +++ b/docs/tr/1.1.2/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.2

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.2/publishing/index.html b/docs/tr/1.1.2/publishing/index.html new file mode 100644 index 0000000000..81abbb718f --- /dev/null +++ b/docs/tr/1.1.2/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.2

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.2/search.html b/docs/tr/1.1.2/search.html new file mode 100644 index 0000000000..213f91c20a --- /dev/null +++ b/docs/tr/1.1.2/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.2

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.2/search/index.html b/docs/tr/1.1.2/search/index.html new file mode 100644 index 0000000000..213f91c20a --- /dev/null +++ b/docs/tr/1.1.2/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.2

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.2/site-config.html b/docs/tr/1.1.2/site-config.html new file mode 100644 index 0000000000..3dccd10b90 --- /dev/null +++ b/docs/tr/1.1.2/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.2

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.2/site-config/index.html b/docs/tr/1.1.2/site-config/index.html new file mode 100644 index 0000000000..3dccd10b90 --- /dev/null +++ b/docs/tr/1.1.2/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.2

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.2/site-creation.html b/docs/tr/1.1.2/site-creation.html new file mode 100644 index 0000000000..c0f1f6f3e0 --- /dev/null +++ b/docs/tr/1.1.2/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.2

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.2/site-creation/index.html b/docs/tr/1.1.2/site-creation/index.html new file mode 100644 index 0000000000..c0f1f6f3e0 --- /dev/null +++ b/docs/tr/1.1.2/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.2

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.2/site-preparation.html b/docs/tr/1.1.2/site-preparation.html new file mode 100644 index 0000000000..07006175a3 --- /dev/null +++ b/docs/tr/1.1.2/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.2

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.2/site-preparation/index.html b/docs/tr/1.1.2/site-preparation/index.html new file mode 100644 index 0000000000..07006175a3 --- /dev/null +++ b/docs/tr/1.1.2/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.2

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.2/translation.html b/docs/tr/1.1.2/translation.html new file mode 100644 index 0000000000..1a65d57b07 --- /dev/null +++ b/docs/tr/1.1.2/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.2

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.2/translation/index.html b/docs/tr/1.1.2/translation/index.html new file mode 100644 index 0000000000..1a65d57b07 --- /dev/null +++ b/docs/tr/1.1.2/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.2

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.2/versioning.html b/docs/tr/1.1.2/versioning.html new file mode 100644 index 0000000000..0c8c1725fd --- /dev/null +++ b/docs/tr/1.1.2/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.2

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.2/versioning/index.html b/docs/tr/1.1.2/versioning/index.html new file mode 100644 index 0000000000..0c8c1725fd --- /dev/null +++ b/docs/tr/1.1.2/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.2

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.3/api-pages.html b/docs/tr/1.1.3/api-pages.html new file mode 100644 index 0000000000..a3a598a9d2 --- /dev/null +++ b/docs/tr/1.1.3/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.3

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.3/api-pages/index.html b/docs/tr/1.1.3/api-pages/index.html new file mode 100644 index 0000000000..a3a598a9d2 --- /dev/null +++ b/docs/tr/1.1.3/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.3

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.3/blog.html b/docs/tr/1.1.3/blog.html new file mode 100644 index 0000000000..19eabbfdbd --- /dev/null +++ b/docs/tr/1.1.3/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.3

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.3/blog/index.html b/docs/tr/1.1.3/blog/index.html new file mode 100644 index 0000000000..19eabbfdbd --- /dev/null +++ b/docs/tr/1.1.3/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.3

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.3/commands.html b/docs/tr/1.1.3/commands.html new file mode 100644 index 0000000000..e0613e73c3 --- /dev/null +++ b/docs/tr/1.1.3/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.3

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.3/commands/index.html b/docs/tr/1.1.3/commands/index.html new file mode 100644 index 0000000000..e0613e73c3 --- /dev/null +++ b/docs/tr/1.1.3/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.3

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.3/custom-pages.html b/docs/tr/1.1.3/custom-pages.html new file mode 100644 index 0000000000..71cce82d5d --- /dev/null +++ b/docs/tr/1.1.3/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.3

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.3/custom-pages/index.html b/docs/tr/1.1.3/custom-pages/index.html new file mode 100644 index 0000000000..71cce82d5d --- /dev/null +++ b/docs/tr/1.1.3/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.3

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.3/doc-markdown.html b/docs/tr/1.1.3/doc-markdown.html new file mode 100644 index 0000000000..da088ed534 --- /dev/null +++ b/docs/tr/1.1.3/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.3

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.3/doc-markdown/index.html b/docs/tr/1.1.3/doc-markdown/index.html new file mode 100644 index 0000000000..da088ed534 --- /dev/null +++ b/docs/tr/1.1.3/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.3

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.3/installation.html b/docs/tr/1.1.3/installation.html new file mode 100644 index 0000000000..4609b99b03 --- /dev/null +++ b/docs/tr/1.1.3/installation.html @@ -0,0 +1,112 @@ +Installation · Docusaurus

1.1.3

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   └── 2017-04-10-blog-post-two.md
+    ├── core
+    │   └── Footer.js
+    ├── node_modules
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.3/installation/index.html b/docs/tr/1.1.3/installation/index.html new file mode 100644 index 0000000000..4609b99b03 --- /dev/null +++ b/docs/tr/1.1.3/installation/index.html @@ -0,0 +1,112 @@ +Installation · Docusaurus

1.1.3

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   └── 2017-04-10-blog-post-two.md
+    ├── core
+    │   └── Footer.js
+    ├── node_modules
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.3/navigation.html b/docs/tr/1.1.3/navigation.html new file mode 100644 index 0000000000..b713a84b58 --- /dev/null +++ b/docs/tr/1.1.3/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.3

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.3/navigation/index.html b/docs/tr/1.1.3/navigation/index.html new file mode 100644 index 0000000000..b713a84b58 --- /dev/null +++ b/docs/tr/1.1.3/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.3

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.3/publishing.html b/docs/tr/1.1.3/publishing.html new file mode 100644 index 0000000000..72b5736ee3 --- /dev/null +++ b/docs/tr/1.1.3/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.3

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.3/publishing/index.html b/docs/tr/1.1.3/publishing/index.html new file mode 100644 index 0000000000..72b5736ee3 --- /dev/null +++ b/docs/tr/1.1.3/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.3

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.3/search.html b/docs/tr/1.1.3/search.html new file mode 100644 index 0000000000..59f353c1ef --- /dev/null +++ b/docs/tr/1.1.3/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.3

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.3/search/index.html b/docs/tr/1.1.3/search/index.html new file mode 100644 index 0000000000..59f353c1ef --- /dev/null +++ b/docs/tr/1.1.3/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.3

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.3/site-config.html b/docs/tr/1.1.3/site-config.html new file mode 100644 index 0000000000..bb2c3a574b --- /dev/null +++ b/docs/tr/1.1.3/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.3

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.3/site-config/index.html b/docs/tr/1.1.3/site-config/index.html new file mode 100644 index 0000000000..bb2c3a574b --- /dev/null +++ b/docs/tr/1.1.3/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.3

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.3/site-creation.html b/docs/tr/1.1.3/site-creation.html new file mode 100644 index 0000000000..b916f9a062 --- /dev/null +++ b/docs/tr/1.1.3/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.3

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.3/site-creation/index.html b/docs/tr/1.1.3/site-creation/index.html new file mode 100644 index 0000000000..b916f9a062 --- /dev/null +++ b/docs/tr/1.1.3/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.3

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.3/site-preparation.html b/docs/tr/1.1.3/site-preparation.html new file mode 100644 index 0000000000..84dec3bace --- /dev/null +++ b/docs/tr/1.1.3/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.3

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.3/site-preparation/index.html b/docs/tr/1.1.3/site-preparation/index.html new file mode 100644 index 0000000000..84dec3bace --- /dev/null +++ b/docs/tr/1.1.3/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.3

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.3/translation.html b/docs/tr/1.1.3/translation.html new file mode 100644 index 0000000000..1946c6d8d3 --- /dev/null +++ b/docs/tr/1.1.3/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.3

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.3/translation/index.html b/docs/tr/1.1.3/translation/index.html new file mode 100644 index 0000000000..1946c6d8d3 --- /dev/null +++ b/docs/tr/1.1.3/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.3

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.3/versioning.html b/docs/tr/1.1.3/versioning.html new file mode 100644 index 0000000000..6689a1a234 --- /dev/null +++ b/docs/tr/1.1.3/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.3

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.3/versioning/index.html b/docs/tr/1.1.3/versioning/index.html new file mode 100644 index 0000000000..6689a1a234 --- /dev/null +++ b/docs/tr/1.1.3/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.3

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.4/api-pages.html b/docs/tr/1.1.4/api-pages.html new file mode 100644 index 0000000000..a0ac986bbb --- /dev/null +++ b/docs/tr/1.1.4/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.4

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.4/api-pages/index.html b/docs/tr/1.1.4/api-pages/index.html new file mode 100644 index 0000000000..a0ac986bbb --- /dev/null +++ b/docs/tr/1.1.4/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.4

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.4/blog.html b/docs/tr/1.1.4/blog.html new file mode 100644 index 0000000000..b367abc4b0 --- /dev/null +++ b/docs/tr/1.1.4/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.4

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.4/blog/index.html b/docs/tr/1.1.4/blog/index.html new file mode 100644 index 0000000000..b367abc4b0 --- /dev/null +++ b/docs/tr/1.1.4/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.4

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.4/commands.html b/docs/tr/1.1.4/commands.html new file mode 100644 index 0000000000..0e6334e233 --- /dev/null +++ b/docs/tr/1.1.4/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.4

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.4/commands/index.html b/docs/tr/1.1.4/commands/index.html new file mode 100644 index 0000000000..0e6334e233 --- /dev/null +++ b/docs/tr/1.1.4/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.4

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.4/custom-pages.html b/docs/tr/1.1.4/custom-pages.html new file mode 100644 index 0000000000..49f51e32c6 --- /dev/null +++ b/docs/tr/1.1.4/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.4

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.4/custom-pages/index.html b/docs/tr/1.1.4/custom-pages/index.html new file mode 100644 index 0000000000..49f51e32c6 --- /dev/null +++ b/docs/tr/1.1.4/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.4

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.4/doc-markdown.html b/docs/tr/1.1.4/doc-markdown.html new file mode 100644 index 0000000000..055caf98d4 --- /dev/null +++ b/docs/tr/1.1.4/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.4

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.4/doc-markdown/index.html b/docs/tr/1.1.4/doc-markdown/index.html new file mode 100644 index 0000000000..055caf98d4 --- /dev/null +++ b/docs/tr/1.1.4/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.4

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.4/installation.html b/docs/tr/1.1.4/installation.html new file mode 100644 index 0000000000..440c7809f4 --- /dev/null +++ b/docs/tr/1.1.4/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.4

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.4/installation/index.html b/docs/tr/1.1.4/installation/index.html new file mode 100644 index 0000000000..440c7809f4 --- /dev/null +++ b/docs/tr/1.1.4/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.4

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.4/navigation.html b/docs/tr/1.1.4/navigation.html new file mode 100644 index 0000000000..bb89df22f5 --- /dev/null +++ b/docs/tr/1.1.4/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.4

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.4/navigation/index.html b/docs/tr/1.1.4/navigation/index.html new file mode 100644 index 0000000000..bb89df22f5 --- /dev/null +++ b/docs/tr/1.1.4/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.4

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.4/publishing.html b/docs/tr/1.1.4/publishing.html new file mode 100644 index 0000000000..576a0ae16f --- /dev/null +++ b/docs/tr/1.1.4/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.4

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.4/publishing/index.html b/docs/tr/1.1.4/publishing/index.html new file mode 100644 index 0000000000..576a0ae16f --- /dev/null +++ b/docs/tr/1.1.4/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.4

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.4/search.html b/docs/tr/1.1.4/search.html new file mode 100644 index 0000000000..45ea192482 --- /dev/null +++ b/docs/tr/1.1.4/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.4

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.4/search/index.html b/docs/tr/1.1.4/search/index.html new file mode 100644 index 0000000000..45ea192482 --- /dev/null +++ b/docs/tr/1.1.4/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.4

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.4/site-config.html b/docs/tr/1.1.4/site-config.html new file mode 100644 index 0000000000..9d56f98563 --- /dev/null +++ b/docs/tr/1.1.4/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.4

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.4/site-config/index.html b/docs/tr/1.1.4/site-config/index.html new file mode 100644 index 0000000000..9d56f98563 --- /dev/null +++ b/docs/tr/1.1.4/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.4

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.4/site-creation.html b/docs/tr/1.1.4/site-creation.html new file mode 100644 index 0000000000..a5bea69991 --- /dev/null +++ b/docs/tr/1.1.4/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.4

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.4/site-creation/index.html b/docs/tr/1.1.4/site-creation/index.html new file mode 100644 index 0000000000..a5bea69991 --- /dev/null +++ b/docs/tr/1.1.4/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.4

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.4/site-preparation.html b/docs/tr/1.1.4/site-preparation.html new file mode 100644 index 0000000000..c028a66295 --- /dev/null +++ b/docs/tr/1.1.4/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.4

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.4/site-preparation/index.html b/docs/tr/1.1.4/site-preparation/index.html new file mode 100644 index 0000000000..c028a66295 --- /dev/null +++ b/docs/tr/1.1.4/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.4

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.4/translation.html b/docs/tr/1.1.4/translation.html new file mode 100644 index 0000000000..730666bdb1 --- /dev/null +++ b/docs/tr/1.1.4/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.4

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.4/translation/index.html b/docs/tr/1.1.4/translation/index.html new file mode 100644 index 0000000000..730666bdb1 --- /dev/null +++ b/docs/tr/1.1.4/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.4

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.4/versioning.html b/docs/tr/1.1.4/versioning.html new file mode 100644 index 0000000000..42f41a76f6 --- /dev/null +++ b/docs/tr/1.1.4/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.4

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.4/versioning/index.html b/docs/tr/1.1.4/versioning/index.html new file mode 100644 index 0000000000..42f41a76f6 --- /dev/null +++ b/docs/tr/1.1.4/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.4

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.5/api-pages.html b/docs/tr/1.1.5/api-pages.html new file mode 100644 index 0000000000..cb313d7e84 --- /dev/null +++ b/docs/tr/1.1.5/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.5

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.5/api-pages/index.html b/docs/tr/1.1.5/api-pages/index.html new file mode 100644 index 0000000000..cb313d7e84 --- /dev/null +++ b/docs/tr/1.1.5/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.5

Translate

Pages and Styles

Docusaurus sayfaları React bileşenleri olarak sitenin geri kalanı ile aynı başlık, altbilgi ve stilleri paylaşan website/sayfalar klasörü içine yazmanıza olanak sağlar.

+

URLs for Pages

+

website/sayfalar içerisindeki herhangi bir .js dosyası "sayfalar" dosyasından sonraki yolu kullanarak statik html'e çevrilir. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. Örnek olarak, website/sayfalar/ing/yardım.js sayfası için dosya ${baseUrl}ing/yardım.js url'sinde bulunacaktır aynı zamanda ${baseUrl} içerisindeki ${baseUrl}yardım.js url'si siteConfig.js dosyası içerisinde ayarlı bazUrl alanıdır.

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.1.5/blog.html b/docs/tr/1.1.5/blog.html new file mode 100644 index 0000000000..9d726aba4a --- /dev/null +++ b/docs/tr/1.1.5/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.5

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.5/blog/index.html b/docs/tr/1.1.5/blog/index.html new file mode 100644 index 0000000000..9d726aba4a --- /dev/null +++ b/docs/tr/1.1.5/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.5

Translate

Adding a Blog

İlk Kurulum

+

Sitenizin blog'unu kurmak için, deponuzun website dizinine blog klasörünü oluşturmakla başlayın.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Yayınlanan tüm blog paylaşımları incelenirken bu paylaşımınızın özet olarak neresinin gösterileceğini belirtmek için <!--truncate--> işaretleyicisini kullanın. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL'
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.1.5/commands.html b/docs/tr/1.1.5/commands.html new file mode 100644 index 0000000000..5fa4549449 --- /dev/null +++ b/docs/tr/1.1.5/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.5

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.5/commands/index.html b/docs/tr/1.1.5/commands/index.html new file mode 100644 index 0000000000..5fa4549449 --- /dev/null +++ b/docs/tr/1.1.5/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.5

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.1.5/custom-pages.html b/docs/tr/1.1.5/custom-pages.html new file mode 100644 index 0000000000..101616c233 --- /dev/null +++ b/docs/tr/1.1.5/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.5

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.5/custom-pages/index.html b/docs/tr/1.1.5/custom-pages/index.html new file mode 100644 index 0000000000..101616c233 --- /dev/null +++ b/docs/tr/1.1.5/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.5

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. Alternatif olarak, pages klasörüne de eklenebilirler ve React tarafından işlenmek yerine oldukları gibi kullanılmalıdırlar.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.1.5/doc-markdown.html b/docs/tr/1.1.5/doc-markdown.html new file mode 100644 index 0000000000..b953fd9964 --- /dev/null +++ b/docs/tr/1.1.5/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.5

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.5/doc-markdown/index.html b/docs/tr/1.1.5/doc-markdown/index.html new file mode 100644 index 0000000000..b953fd9964 --- /dev/null +++ b/docs/tr/1.1.5/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.5

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog Postları her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

Diğer dokümantasyon dosyaları için bunlar, işlenerek otomatik olarak karşılık gelen html bağlantılarına dönüştürülen diğer dokümantasyon dosyaları ile ilişkili bağlantılar kullanabilirsiniz.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

Bu bağlantılar diğer dokümanlar (hala GitHub içerisinde) için çalışan bağlantılar olacağından GitHub dosyaları arasında dolaşmak istediğinizde işe yarayacaktır ama ama dokümanlar işlendiklerinde doğru html bağlantılarına sahip olacaklar.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Statik varlıklar dokümanlarla gibi ilişkili url'leri kullanarak bağlantılanabilirler. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

API belgeleri için içeriklerin bir tablosu olarak kullanışlı olabilen otomatik oluşturulan linklerin bir listesini yapabilirsiniz.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.1.5/installation.html b/docs/tr/1.1.5/installation.html new file mode 100644 index 0000000000..66a810738b --- /dev/null +++ b/docs/tr/1.1.5/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.5

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.5/installation/index.html b/docs/tr/1.1.5/installation/index.html new file mode 100644 index 0000000000..66a810738b --- /dev/null +++ b/docs/tr/1.1.5/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.5

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    While we recommend Node 8.x or greater, your Node version must at least 6.x.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.1.5/navigation.html b/docs/tr/1.1.5/navigation.html new file mode 100644 index 0000000000..77ffdecad0 --- /dev/null +++ b/docs/tr/1.1.5/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.5

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.5/navigation/index.html b/docs/tr/1.1.5/navigation/index.html new file mode 100644 index 0000000000..77ffdecad0 --- /dev/null +++ b/docs/tr/1.1.5/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.5

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.1.5/publishing.html b/docs/tr/1.1.5/publishing.html new file mode 100644 index 0000000000..c49ffb8a11 --- /dev/null +++ b/docs/tr/1.1.5/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.5

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.5/publishing/index.html b/docs/tr/1.1.5/publishing/index.html new file mode 100644 index 0000000000..c49ffb8a11 --- /dev/null +++ b/docs/tr/1.1.5/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.5

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.1.5/search.html b/docs/tr/1.1.5/search.html new file mode 100644 index 0000000000..5f3db7af3e --- /dev/null +++ b/docs/tr/1.1.5/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.5

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.5/search/index.html b/docs/tr/1.1.5/search/index.html new file mode 100644 index 0000000000..5f3db7af3e --- /dev/null +++ b/docs/tr/1.1.5/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.5

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.1.5/site-config.html b/docs/tr/1.1.5/site-config.html new file mode 100644 index 0000000000..6ad4be5137 --- /dev/null +++ b/docs/tr/1.1.5/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.5

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.5/site-config/index.html b/docs/tr/1.1.5/site-config/index.html new file mode 100644 index 0000000000..6ad4be5137 --- /dev/null +++ b/docs/tr/1.1.5/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.5

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - Kısayol simgesi için url.

+

headerIcon - Başlık gezinme çubuğunda kullanılan simge için url.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - url for your site.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.1.5/site-creation.html b/docs/tr/1.1.5/site-creation.html new file mode 100644 index 0000000000..b0506f03ef --- /dev/null +++ b/docs/tr/1.1.5/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.5

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.5/site-creation/index.html b/docs/tr/1.1.5/site-creation/index.html new file mode 100644 index 0000000000..b0506f03ef --- /dev/null +++ b/docs/tr/1.1.5/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.5

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Resimler gibi varlıkları website/static/ klasörüne yerleştirin.

    6. +

  6. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.1.5/site-preparation.html b/docs/tr/1.1.5/site-preparation.html new file mode 100644 index 0000000000..9503569727 --- /dev/null +++ b/docs/tr/1.1.5/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.5

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.5/site-preparation/index.html b/docs/tr/1.1.5/site-preparation/index.html new file mode 100644 index 0000000000..9503569727 --- /dev/null +++ b/docs/tr/1.1.5/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.5

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • website/blog-examples-from-docusaurus klasörü markdown ile yazılmış blog postlarının örneklerini içerir.
    • +
  • docs-examples-from-docusaurusklasörü markdown ile yazılmış örnek belgeleme dosyaları içerir.
    • +
  • website/pages klasörü site için örnek üst seviye sayfalar içerir.
    • +
  • website/static klasörü örnek siteye göre statik değerler içerir.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

website/pages ve website/static klasörlerini sürdürmelisiniz fakat içlerindeki içeriği istediğiniz gibi değiştirebilirsiniz. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.1.5/translation.html b/docs/tr/1.1.5/translation.html new file mode 100644 index 0000000000..c3755e9ab1 --- /dev/null +++ b/docs/tr/1.1.5/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.5

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.5/translation/index.html b/docs/tr/1.1.5/translation/index.html new file mode 100644 index 0000000000..c3755e9ab1 --- /dev/null +++ b/docs/tr/1.1.5/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.5

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Çevirmek istediğiniz metne sahip sayfalar website/pages/en klasörüne yerleştirilmelidir.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.1.5/versioning.html b/docs/tr/1.1.5/versioning.html new file mode 100644 index 0000000000..4c5733f01d --- /dev/null +++ b/docs/tr/1.1.5/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.5

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.1.5/versioning/index.html b/docs/tr/1.1.5/versioning/index.html new file mode 100644 index 0000000000..4c5733f01d --- /dev/null +++ b/docs/tr/1.1.5/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.5

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs folder. Bu belirli dokümantasyon seti saklanacak ve docs klasöründeki dokümantasyonda değişiklikler yapılsa bile erişilebilir olacaktır.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

Bu şu anda docs klasöründe bulunan tüm dokümanları saklar ve onları sürüm 1.0.0 dokümantasyonları olarak erişilebilir yapar.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

docs klasöründeki dokümanlar next sürümünün parçası olarak kabul edilir ve, örnek olarak, docs/next/doc1.html url'sinden ulaşılabilirler. En son sürümdeki dokümantasyon docs/doc1.html url'sini kullanır.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. 1.0.0 sürümü dokümantasyonu docs/1.0.0/doc1.html url'sini kullanırken 2.0.0 sürümü docs/doc1.html'yi kullanacaktır.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.2.0/api-pages.html b/docs/tr/1.2.0/api-pages.html new file mode 100644 index 0000000000..dbf03995b0 --- /dev/null +++ b/docs/tr/1.2.0/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.2.0/api-pages/index.html b/docs/tr/1.2.0/api-pages/index.html new file mode 100644 index 0000000000..dbf03995b0 --- /dev/null +++ b/docs/tr/1.2.0/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.2.0/blog.html b/docs/tr/1.2.0/blog.html new file mode 100644 index 0000000000..dd334c2356 --- /dev/null +++ b/docs/tr/1.2.0/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.2.0

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.2.0/blog/index.html b/docs/tr/1.2.0/blog/index.html new file mode 100644 index 0000000000..dd334c2356 --- /dev/null +++ b/docs/tr/1.2.0/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.2.0

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.2.0/commands.html b/docs/tr/1.2.0/commands.html new file mode 100644 index 0000000000..dd453599ac --- /dev/null +++ b/docs/tr/1.2.0/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.2.0

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.2.0/commands/index.html b/docs/tr/1.2.0/commands/index.html new file mode 100644 index 0000000000..dd453599ac --- /dev/null +++ b/docs/tr/1.2.0/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.2.0

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.2.0/custom-pages.html b/docs/tr/1.2.0/custom-pages.html new file mode 100644 index 0000000000..7da620ff18 --- /dev/null +++ b/docs/tr/1.2.0/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.2.0/custom-pages/index.html b/docs/tr/1.2.0/custom-pages/index.html new file mode 100644 index 0000000000..7da620ff18 --- /dev/null +++ b/docs/tr/1.2.0/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.2.0/doc-markdown.html b/docs/tr/1.2.0/doc-markdown.html new file mode 100644 index 0000000000..99e28ee53a --- /dev/null +++ b/docs/tr/1.2.0/doc-markdown.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.0

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.2.0/doc-markdown/index.html b/docs/tr/1.2.0/doc-markdown/index.html new file mode 100644 index 0000000000..99e28ee53a --- /dev/null +++ b/docs/tr/1.2.0/doc-markdown/index.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.0

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.2.0/installation.html b/docs/tr/1.2.0/installation.html new file mode 100644 index 0000000000..e984c79455 --- /dev/null +++ b/docs/tr/1.2.0/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.2.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.2.0/installation/index.html b/docs/tr/1.2.0/installation/index.html new file mode 100644 index 0000000000..e984c79455 --- /dev/null +++ b/docs/tr/1.2.0/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.2.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.2.0/navigation.html b/docs/tr/1.2.0/navigation.html new file mode 100644 index 0000000000..9486128aa1 --- /dev/null +++ b/docs/tr/1.2.0/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.2.0/navigation/index.html b/docs/tr/1.2.0/navigation/index.html new file mode 100644 index 0000000000..9486128aa1 --- /dev/null +++ b/docs/tr/1.2.0/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.2.0/publishing.html b/docs/tr/1.2.0/publishing.html new file mode 100644 index 0000000000..1684100c30 --- /dev/null +++ b/docs/tr/1.2.0/publishing.html @@ -0,0 +1,255 @@ +Publishing your site · Docusaurus

1.2.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.2.0/publishing/index.html b/docs/tr/1.2.0/publishing/index.html new file mode 100644 index 0000000000..1684100c30 --- /dev/null +++ b/docs/tr/1.2.0/publishing/index.html @@ -0,0 +1,255 @@ +Publishing your site · Docusaurus

1.2.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.2.0/search.html b/docs/tr/1.2.0/search.html new file mode 100644 index 0000000000..ce3ed92f5a --- /dev/null +++ b/docs/tr/1.2.0/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.2.0

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.2.0/search/index.html b/docs/tr/1.2.0/search/index.html new file mode 100644 index 0000000000..ce3ed92f5a --- /dev/null +++ b/docs/tr/1.2.0/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.2.0

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.2.0/site-config.html b/docs/tr/1.2.0/site-config.html new file mode 100644 index 0000000000..405e3c9db8 --- /dev/null +++ b/docs/tr/1.2.0/site-config.html @@ -0,0 +1,257 @@ +siteConfig.js · Docusaurus

1.2.0

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.2.0/site-config/index.html b/docs/tr/1.2.0/site-config/index.html new file mode 100644 index 0000000000..405e3c9db8 --- /dev/null +++ b/docs/tr/1.2.0/site-config/index.html @@ -0,0 +1,257 @@ +siteConfig.js · Docusaurus

1.2.0

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.2.0/site-creation.html b/docs/tr/1.2.0/site-creation.html new file mode 100644 index 0000000000..a9691f9be8 --- /dev/null +++ b/docs/tr/1.2.0/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.2.0/site-creation/index.html b/docs/tr/1.2.0/site-creation/index.html new file mode 100644 index 0000000000..a9691f9be8 --- /dev/null +++ b/docs/tr/1.2.0/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.2.0/site-preparation.html b/docs/tr/1.2.0/site-preparation.html new file mode 100644 index 0000000000..27ac25c2f3 --- /dev/null +++ b/docs/tr/1.2.0/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.2.0/site-preparation/index.html b/docs/tr/1.2.0/site-preparation/index.html new file mode 100644 index 0000000000..27ac25c2f3 --- /dev/null +++ b/docs/tr/1.2.0/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.2.0/translation.html b/docs/tr/1.2.0/translation.html new file mode 100644 index 0000000000..b1011706a4 --- /dev/null +++ b/docs/tr/1.2.0/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.2.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.2.0/translation/index.html b/docs/tr/1.2.0/translation/index.html new file mode 100644 index 0000000000..b1011706a4 --- /dev/null +++ b/docs/tr/1.2.0/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.2.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.2.0/versioning.html b/docs/tr/1.2.0/versioning.html new file mode 100644 index 0000000000..ff763c2d37 --- /dev/null +++ b/docs/tr/1.2.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.2.0/versioning/index.html b/docs/tr/1.2.0/versioning/index.html new file mode 100644 index 0000000000..ff763c2d37 --- /dev/null +++ b/docs/tr/1.2.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.2.1/api-pages.html b/docs/tr/1.2.1/api-pages.html new file mode 100644 index 0000000000..93d08a3221 --- /dev/null +++ b/docs/tr/1.2.1/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.2.1/api-pages/index.html b/docs/tr/1.2.1/api-pages/index.html new file mode 100644 index 0000000000..93d08a3221 --- /dev/null +++ b/docs/tr/1.2.1/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.2.1/blog.html b/docs/tr/1.2.1/blog.html new file mode 100644 index 0000000000..48196dc3c4 --- /dev/null +++ b/docs/tr/1.2.1/blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.2.1

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.2.1/blog/index.html b/docs/tr/1.2.1/blog/index.html new file mode 100644 index 0000000000..48196dc3c4 --- /dev/null +++ b/docs/tr/1.2.1/blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.2.1

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.2.1/commands.html b/docs/tr/1.2.1/commands.html new file mode 100644 index 0000000000..b9531e873e --- /dev/null +++ b/docs/tr/1.2.1/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.2.1

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.2.1/commands/index.html b/docs/tr/1.2.1/commands/index.html new file mode 100644 index 0000000000..b9531e873e --- /dev/null +++ b/docs/tr/1.2.1/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.2.1

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.2.1/custom-pages.html b/docs/tr/1.2.1/custom-pages.html new file mode 100644 index 0000000000..cbd313df56 --- /dev/null +++ b/docs/tr/1.2.1/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.2.1/custom-pages/index.html b/docs/tr/1.2.1/custom-pages/index.html new file mode 100644 index 0000000000..cbd313df56 --- /dev/null +++ b/docs/tr/1.2.1/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← ÖncekiEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.2.1/doc-markdown.html b/docs/tr/1.2.1/doc-markdown.html new file mode 100644 index 0000000000..0ed95c7ff5 --- /dev/null +++ b/docs/tr/1.2.1/doc-markdown.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.1

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.2.1/doc-markdown/index.html b/docs/tr/1.2.1/doc-markdown/index.html new file mode 100644 index 0000000000..0ed95c7ff5 --- /dev/null +++ b/docs/tr/1.2.1/doc-markdown/index.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.1

Translate

Markdown Features

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.2.1/installation.html b/docs/tr/1.2.1/installation.html new file mode 100644 index 0000000000..103f95509f --- /dev/null +++ b/docs/tr/1.2.1/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.2.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.2.1/installation/index.html b/docs/tr/1.2.1/installation/index.html new file mode 100644 index 0000000000..103f95509f --- /dev/null +++ b/docs/tr/1.2.1/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.2.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.2.1/navigation.html b/docs/tr/1.2.1/navigation.html new file mode 100644 index 0000000000..8edb545771 --- /dev/null +++ b/docs/tr/1.2.1/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.2.1/navigation/index.html b/docs/tr/1.2.1/navigation/index.html new file mode 100644 index 0000000000..8edb545771 --- /dev/null +++ b/docs/tr/1.2.1/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.2.1/publishing.html b/docs/tr/1.2.1/publishing.html new file mode 100644 index 0000000000..432115bf05 --- /dev/null +++ b/docs/tr/1.2.1/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.2.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.2.1/publishing/index.html b/docs/tr/1.2.1/publishing/index.html new file mode 100644 index 0000000000..432115bf05 --- /dev/null +++ b/docs/tr/1.2.1/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.2.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteSonraki →
\ No newline at end of file diff --git a/docs/tr/1.2.1/search.html b/docs/tr/1.2.1/search.html new file mode 100644 index 0000000000..6da956412d --- /dev/null +++ b/docs/tr/1.2.1/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.2.1

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.2.1/search/index.html b/docs/tr/1.2.1/search/index.html new file mode 100644 index 0000000000..6da956412d --- /dev/null +++ b/docs/tr/1.2.1/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.2.1

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.2.1/site-config.html b/docs/tr/1.2.1/site-config.html new file mode 100644 index 0000000000..7c5ed3674a --- /dev/null +++ b/docs/tr/1.2.1/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.2.1

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.2.1/site-config/index.html b/docs/tr/1.2.1/site-config/index.html new file mode 100644 index 0000000000..7c5ed3674a --- /dev/null +++ b/docs/tr/1.2.1/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.2.1

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.2.1/site-creation.html b/docs/tr/1.2.1/site-creation.html new file mode 100644 index 0000000000..e79da566d4 --- /dev/null +++ b/docs/tr/1.2.1/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.2.1/site-creation/index.html b/docs/tr/1.2.1/site-creation/index.html new file mode 100644 index 0000000000..e79da566d4 --- /dev/null +++ b/docs/tr/1.2.1/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.2.1/site-preparation.html b/docs/tr/1.2.1/site-preparation.html new file mode 100644 index 0000000000..9b17a4b459 --- /dev/null +++ b/docs/tr/1.2.1/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.2.1/site-preparation/index.html b/docs/tr/1.2.1/site-preparation/index.html new file mode 100644 index 0000000000..9b17a4b459 --- /dev/null +++ b/docs/tr/1.2.1/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.2.1/translation.html b/docs/tr/1.2.1/translation.html new file mode 100644 index 0000000000..b924c132d2 --- /dev/null +++ b/docs/tr/1.2.1/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.2.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.2.1/translation/index.html b/docs/tr/1.2.1/translation/index.html new file mode 100644 index 0000000000..b924c132d2 --- /dev/null +++ b/docs/tr/1.2.1/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.2.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.2.1/versioning.html b/docs/tr/1.2.1/versioning.html new file mode 100644 index 0000000000..c2f03416bb --- /dev/null +++ b/docs/tr/1.2.1/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.2.1/versioning/index.html b/docs/tr/1.2.1/versioning/index.html new file mode 100644 index 0000000000..c2f03416bb --- /dev/null +++ b/docs/tr/1.2.1/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.3.0/adding-blog.html b/docs/tr/1.3.0/adding-blog.html new file mode 100644 index 0000000000..d6e85beba8 --- /dev/null +++ b/docs/tr/1.3.0/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.3.0/adding-blog/index.html b/docs/tr/1.3.0/adding-blog/index.html new file mode 100644 index 0000000000..d6e85beba8 --- /dev/null +++ b/docs/tr/1.3.0/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/1.3.0/api-pages.html b/docs/tr/1.3.0/api-pages.html new file mode 100644 index 0000000000..e26c161cb8 --- /dev/null +++ b/docs/tr/1.3.0/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.3.0/api-pages/index.html b/docs/tr/1.3.0/api-pages/index.html new file mode 100644 index 0000000000..e26c161cb8 --- /dev/null +++ b/docs/tr/1.3.0/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/1.3.0/blog.html b/docs/tr/1.3.0/blog.html new file mode 100644 index 0000000000..186d0f77b8 --- /dev/null +++ b/docs/tr/1.3.0/blog.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/tr/1.3.0/blog/index.html b/docs/tr/1.3.0/blog/index.html new file mode 100644 index 0000000000..186d0f77b8 --- /dev/null +++ b/docs/tr/1.3.0/blog/index.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/tr/1.3.0/commands.html b/docs/tr/1.3.0/commands.html new file mode 100644 index 0000000000..d483fe3d62 --- /dev/null +++ b/docs/tr/1.3.0/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.0

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.3.0/commands/index.html b/docs/tr/1.3.0/commands/index.html new file mode 100644 index 0000000000..d483fe3d62 --- /dev/null +++ b/docs/tr/1.3.0/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.0

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/1.3.0/custom-pages.html b/docs/tr/1.3.0/custom-pages.html new file mode 100644 index 0000000000..057eba2fdd --- /dev/null +++ b/docs/tr/1.3.0/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.3.0/custom-pages/index.html b/docs/tr/1.3.0/custom-pages/index.html new file mode 100644 index 0000000000..057eba2fdd --- /dev/null +++ b/docs/tr/1.3.0/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/tr/1.3.0/doc-markdown.html b/docs/tr/1.3.0/doc-markdown.html new file mode 100644 index 0000000000..890692277c --- /dev/null +++ b/docs/tr/1.3.0/doc-markdown.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.0

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.3.0/doc-markdown/index.html b/docs/tr/1.3.0/doc-markdown/index.html new file mode 100644 index 0000000000..890692277c --- /dev/null +++ b/docs/tr/1.3.0/doc-markdown/index.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.0

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/1.3.0/installation.html b/docs/tr/1.3.0/installation.html new file mode 100644 index 0000000000..25398b7d8b --- /dev/null +++ b/docs/tr/1.3.0/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.3.0/installation/index.html b/docs/tr/1.3.0/installation/index.html new file mode 100644 index 0000000000..25398b7d8b --- /dev/null +++ b/docs/tr/1.3.0/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.0

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/1.3.0/navigation.html b/docs/tr/1.3.0/navigation.html new file mode 100644 index 0000000000..3778d5b36d --- /dev/null +++ b/docs/tr/1.3.0/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.3.0/navigation/index.html b/docs/tr/1.3.0/navigation/index.html new file mode 100644 index 0000000000..3778d5b36d --- /dev/null +++ b/docs/tr/1.3.0/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/1.3.0/publishing.html b/docs/tr/1.3.0/publishing.html new file mode 100644 index 0000000000..63e7845cea --- /dev/null +++ b/docs/tr/1.3.0/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/tr/1.3.0/publishing/index.html b/docs/tr/1.3.0/publishing/index.html new file mode 100644 index 0000000000..63e7845cea --- /dev/null +++ b/docs/tr/1.3.0/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/tr/1.3.0/search.html b/docs/tr/1.3.0/search.html new file mode 100644 index 0000000000..52422addc3 --- /dev/null +++ b/docs/tr/1.3.0/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.0

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.3.0/search/index.html b/docs/tr/1.3.0/search/index.html new file mode 100644 index 0000000000..52422addc3 --- /dev/null +++ b/docs/tr/1.3.0/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.0

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/1.3.0/site-config.html b/docs/tr/1.3.0/site-config.html new file mode 100644 index 0000000000..2fbc967ee8 --- /dev/null +++ b/docs/tr/1.3.0/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.0

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.3.0/site-config/index.html b/docs/tr/1.3.0/site-config/index.html new file mode 100644 index 0000000000..2fbc967ee8 --- /dev/null +++ b/docs/tr/1.3.0/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.0

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/1.3.0/site-creation.html b/docs/tr/1.3.0/site-creation.html new file mode 100644 index 0000000000..db1546f6b0 --- /dev/null +++ b/docs/tr/1.3.0/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.3.0/site-creation/index.html b/docs/tr/1.3.0/site-creation/index.html new file mode 100644 index 0000000000..db1546f6b0 --- /dev/null +++ b/docs/tr/1.3.0/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/1.3.0/site-preparation.html b/docs/tr/1.3.0/site-preparation.html new file mode 100644 index 0000000000..bb019fd9c3 --- /dev/null +++ b/docs/tr/1.3.0/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.3.0/site-preparation/index.html b/docs/tr/1.3.0/site-preparation/index.html new file mode 100644 index 0000000000..bb019fd9c3 --- /dev/null +++ b/docs/tr/1.3.0/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.0

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/1.3.0/translation.html b/docs/tr/1.3.0/translation.html new file mode 100644 index 0000000000..2aba52641b --- /dev/null +++ b/docs/tr/1.3.0/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.3.0/translation/index.html b/docs/tr/1.3.0/translation/index.html new file mode 100644 index 0000000000..2aba52641b --- /dev/null +++ b/docs/tr/1.3.0/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/1.3.0/versioning.html b/docs/tr/1.3.0/versioning.html new file mode 100644 index 0000000000..a906bf3e7b --- /dev/null +++ b/docs/tr/1.3.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/1.3.0/versioning/index.html b/docs/tr/1.3.0/versioning/index.html new file mode 100644 index 0000000000..a906bf3e7b --- /dev/null +++ b/docs/tr/1.3.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/adding-blog.html b/docs/tr/adding-blog.html new file mode 100644 index 0000000000..98d83e7f4f --- /dev/null +++ b/docs/tr/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/adding-blog/index.html b/docs/tr/adding-blog/index.html new file mode 100644 index 0000000000..98d83e7f4f --- /dev/null +++ b/docs/tr/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/api-pages.html b/docs/tr/api-pages.html new file mode 100644 index 0000000000..27bd3c2b08 --- /dev/null +++ b/docs/tr/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/api-pages/index.html b/docs/tr/api-pages/index.html new file mode 100644 index 0000000000..27bd3c2b08 --- /dev/null +++ b/docs/tr/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/blog.html b/docs/tr/blog.html new file mode 100644 index 0000000000..91b0801e78 --- /dev/null +++ b/docs/tr/blog.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/tr/blog/index.html b/docs/tr/blog/index.html new file mode 100644 index 0000000000..91b0801e78 --- /dev/null +++ b/docs/tr/blog/index.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/tr/commands.html b/docs/tr/commands.html new file mode 100644 index 0000000000..af5b8930a2 --- /dev/null +++ b/docs/tr/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.1

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/commands/index.html b/docs/tr/commands/index.html new file mode 100644 index 0000000000..af5b8930a2 --- /dev/null +++ b/docs/tr/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.1

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/custom-pages.html b/docs/tr/custom-pages.html new file mode 100644 index 0000000000..7adcda4fd7 --- /dev/null +++ b/docs/tr/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/tr/custom-pages/index.html b/docs/tr/custom-pages/index.html new file mode 100644 index 0000000000..7adcda4fd7 --- /dev/null +++ b/docs/tr/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/tr/doc-markdown.html b/docs/tr/doc-markdown.html new file mode 100644 index 0000000000..098daf8637 --- /dev/null +++ b/docs/tr/doc-markdown.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.1

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/doc-markdown/index.html b/docs/tr/doc-markdown/index.html new file mode 100644 index 0000000000..098daf8637 --- /dev/null +++ b/docs/tr/doc-markdown/index.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.1

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/installation.html b/docs/tr/installation.html new file mode 100644 index 0000000000..d3d37babaf --- /dev/null +++ b/docs/tr/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/installation/index.html b/docs/tr/installation/index.html new file mode 100644 index 0000000000..d3d37babaf --- /dev/null +++ b/docs/tr/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.1

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/navigation.html b/docs/tr/navigation.html new file mode 100644 index 0000000000..bf3d0138ec --- /dev/null +++ b/docs/tr/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/navigation/index.html b/docs/tr/navigation/index.html new file mode 100644 index 0000000000..bf3d0138ec --- /dev/null +++ b/docs/tr/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/next/adding-blog.html b/docs/tr/next/adding-blog.html new file mode 100644 index 0000000000..380fb09a53 --- /dev/null +++ b/docs/tr/next/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

next

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/next/adding-blog/index.html b/docs/tr/next/adding-blog/index.html new file mode 100644 index 0000000000..380fb09a53 --- /dev/null +++ b/docs/tr/next/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

next

Translate

Adding a Blog

İlk Kurulum

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

Daha sonra, siteConfig.js içine blog başlık bağlantısı ekleyin:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

Paylaşım Eklemek

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

Örnek olarak, website/blog/2017-08-18-Docusaurus-Tanıtımı.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

Başlık Seçenekleri

+

Tek gerekli alan title; dır fakat blog'unuza yazar bilgilerinizi eklemeniz için seçenekler sağlıyoruz.

+
    +
  • author - Yazar adının bulunduğu metin etiketi.
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

Özet Kesintisi

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate-->'in üstünde kalan herhangi bir şey özetin parçalı olacaktır. Örnek olarak:

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

Changing How Many Blog Posts Show on Sidebar

+

By default, 5 recent blog posts are shown on the sidebar.

+

You can configure a specific amount of blog posts to show by adding a blogSidebarCount setting to your siteConfig.js.

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

Örnek:

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

Örnek:

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS Feed

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+tag.

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+Social Buttons +

+

+ If you want Facebook and/or Twitter social buttons at the bottom of your blog posts, set the facebookAppId and/or twitter site configuration options in siteConfig.js. +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/tr/next/api-pages.html b/docs/tr/next/api-pages.html new file mode 100644 index 0000000000..c6b851b5b1 --- /dev/null +++ b/docs/tr/next/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

next

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/next/api-pages/index.html b/docs/tr/next/api-pages/index.html new file mode 100644 index 0000000000..c6b851b5b1 --- /dev/null +++ b/docs/tr/next/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

next

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/sayfalar/en içindeki dosyalarda aynı zamanda sayfalar'a kopyalanacaktır ve sayfalar içerisindeki aynı adlı dosyaların ÜZERİNE YAZILACAKTIR. For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

Örnek:

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

Örnek:

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/tr/next/commands.html b/docs/tr/next/commands.html new file mode 100644 index 0000000000..b6401e4ce4 --- /dev/null +++ b/docs/tr/next/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

next

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/next/commands/index.html b/docs/tr/next/commands/index.html new file mode 100644 index 0000000000..b6401e4ce4 --- /dev/null +++ b/docs/tr/next/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

next

Translate

CLI Commands

Docusaurus, üretmek, hizmet ve Web sitenizin dağıtmanıza yardımcı olacak komutlar kümesi sağlar. Bu komut dosyalarını run komutuyla Yarn veya npm kullanırken çağırabilir. Sık kullanılan bazı komutlar şunlardır:

+ +

Komut satırından çalıştırma

+

Yarn or npm kullanarak komut dosyalarını çalıştırabilirsiniz. Başlarken kılavuzunu zaten geçtiyseniz; zaten start </ code> komutunu biliyor olabilirsiniz. <code>docusaurus-start komutu Docusaurus'u çalıştırmasını başlatan komuttur. siteyi oluşturan ve bir sunucu başlatan komut dosyası ve genellikle böyle çağrılır:

+
yarn run start
+
+

Aynı komut npm dosyası kullanılarak çağrılabilir:

+
npm run start
+
+

Belirli bir komut dosyası çalıştırmak için, sadece komutunu, start yukarıdaki örneklerde komut dosyanızla ilişkili komutla birlikte kaydedin.

+

Argumentleri kullanmak

+

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
+
+

Şayet npm kullanrak Docusaurus çalıştıyorsanız,komut satırına bağımsız değişkenler ekleyerek komut satırı değişkenlerini kullanmaya devam edebilirsiniz.`` arasındanpm run <command> ve komut argumenleri:

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

Ayarlar

+

Bu komut dosyaları, "scripts" sizin şifreniz website/package.json dosyasını yükleme işleminin bir parçası olarak kullanın. Onları tekrar ayarlama konusunda yardıma ihtiyacınız varsa, Lütfen şunu seçiniz yükleme rehberi.

+

Docusaurus bazı varsayılan eşlemeleri düğümü kuralları aşağıdaki komutları çalıştırmanıza olanak sağlar. Yazarak yerine docusaurus-start every time, you can type yarn run start or npm start.

+

Komutlar

+

<autogenerated_table_of_contents>

+
+

Referans

+

docusaurus-build

+

Eşdeğeri: build.

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

Eşdeğeri: -c

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-publish

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: Açılım işlemesi ile ilişkilendirilmiş git kullanıcısı.
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: CI çalışmasını tetikleyen işleme ilişkili git branşı.
    • +
  • CI_PULL_REQUEST: Geçerli CI çalışması bir çekme isteğindeki bir işlem tarafından tetiklendiğinde doğruluğu beklenir.
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-version <version>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-write-translations

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/tr/next/custom-pages.html b/docs/tr/next/custom-pages.html new file mode 100644 index 0000000000..86c7463689 --- /dev/null +++ b/docs/tr/next/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

next

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/tr/next/custom-pages/index.html b/docs/tr/next/custom-pages/index.html new file mode 100644 index 0000000000..86c7463689 --- /dev/null +++ b/docs/tr/next/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

next

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

Ana Sayfanız Özelleştiriliyor

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. Oradan, website/pages/en/index.js dosyasını ve projeniz için istediğiniz görüntüleri ve metni kullanan değişken bileşenleri düzenleyin.

+

Diğer Özel Sayfalar Ekleniyor

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. Dahili bileşenler hakkında daha fazla bilgi ve kendi bileşenlerinizi nasıl ekleyeceğiniz hakkında bilgiyi burada bulabilirsiniz. Başlık gezinme çubuğunda farklı sayfalar için bağlantıyı nasıl ekleyeceğinizi burada bulabilirsiniz.

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

Statik Sayfalar Eklemek

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

Sitenizin Alt Bilgisini Özelleştirme

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

Sağlanan örnek solunda bir alt bilgi resmi ile birlikte üç sütun ve aşağısında Facebook'un açık kaynak logosu ve telif hakkına sahiptir. Projeniz bir Facebook açık kaynak projesi değilse, logoyu ve telif hakkını kaldırın. Aksi halde, alt bilginizle yaratıcı olun ve onun istediğiniz halde görünmesini sağlayın!

+

Sağlamak isteyebileceğiniz bağlantılar için bir kaç örnek: dokümantasyon, API, Twitter, Discord, Facebook grupları, Stack Overflow, GitHub, vs.

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/tr/next/doc-markdown.html b/docs/tr/next/doc-markdown.html new file mode 100644 index 0000000000..fdc0a311e8 --- /dev/null +++ b/docs/tr/next/doc-markdown.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

next

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/next/doc-markdown/index.html b/docs/tr/next/doc-markdown/index.html new file mode 100644 index 0000000000..fdc0a311e8 --- /dev/null +++ b/docs/tr/next/doc-markdown/index.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

next

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown Başlıkları

+

Döküman

+

Belgeler her iki tarafta bir çizgi --- ile kuşatılmış aşağıdaki markdown başlık alanlarını kullanır:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

Örnek olarak:

+
---
+id: dök1
+title: Benim Dokümanım
+sidebar_label: Doküman
+---
+
+

Kimliğe sahip sürümlenmiş dokümanlar kopyalanırken sürüm numaralarını içerecek şekilde değiştirilirler. O dokümanın versiyon numarası ${version} ve orijinal id'si ${id} olduğu yerde yeni id version-${version}-${id}'dir. Ek olarak, sürümlenen dokümanlara, orijinal doküman kimliğine sahip original_id alanı eklenir.

+

Örnek olarak:

+
---
+id: version-1.0.0-doc1
+title: Dokumanım
+sidebar_label: Doküman
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

Örnek olarak:

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

Blog Postları

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

title: Bu blog postunun başlığı.

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: Yazarım Facebook kimliği, sadece blog da gösterilmek için yazarın profil resmine erişim için kullanılıyor. Eğer bu alan ihmal edilmişse blog paylaşımında hiçbir yazar resmi gösterilmeyecektir.

+

Örnek olarak:

+
---
+title: İlk Blog Paylaşımım
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

Ekstra Özellikler

+

Docusaurus markdown ile doküman yazarken bir kaç ek özellik destekler.

+

Diğer Dokümanlara Bağlantılamak

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

Örnek:

+
[Bu diğer dokümanın bağlantısı](diger-dokuman.md)
+
+

Bu markdown işlendikten sonra otomatik olarak /docs/other-document.html(yada uygun olarak çevrilmiş/sürümlenmiş bağlantıya) bağlantısına dönüşür.

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

Resimlere ve Diğer Varlıklara Bağlantılama

+

Static assets can be linked to in the same way that documents are, using relative URLs. Dokümanlar ve bloglar da kullanılan statik varlıklar sırasıyla docs/assets ve website/blog/assets içerisine gitmelidirler. Markdown doğru bağlantı yoluna çevrilecektir böylece bu yollar dokümanların tüm dilleri ve sürümleri için çalışacaktır.

+

Örnek:

+
![alt-text](/docs/assets/doc-image.png)
+
+

İçerik Panosu Üretme

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. Dokümanınızı kod bloğu içerisindeki her fonksiyon için h3 başlığını kullanarak yazın. These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

Örnek:

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

bu fonksiyonun içerik panosuna yönlendirir:

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

ve her fonksiyon kendilerinin karşılık gelen sayfasına bağlanır.

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

Örnek:

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/tr/next/installation.html b/docs/tr/next/installation.html new file mode 100644 index 0000000000..4fb5397e3a --- /dev/null +++ b/docs/tr/next/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

next

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/next/installation/index.html b/docs/tr/next/installation/index.html new file mode 100644 index 0000000000..4fb5397e3a --- /dev/null +++ b/docs/tr/next/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

next

Translate

Installation

Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. Go into the root of your GitHub repo directory where you will be creating the docs.

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

Kurulumu doğrulama

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. In your root, rename docs-examples-from-docusaurus to docs.
    2. +
  2. cd website
    3. +
  3. Rename blog-examples-from-docusaurus to blog.
    4. +
  4. Run the local webserver via yarn start or npm start.
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

yada

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/tr/next/navigation.html b/docs/tr/next/navigation.html new file mode 100644 index 0000000000..64ac2c6496 --- /dev/null +++ b/docs/tr/next/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

next

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/next/navigation/index.html b/docs/tr/next/navigation/index.html new file mode 100644 index 0000000000..64ac2c6496 --- /dev/null +++ b/docs/tr/next/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

next

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Veya yan bar içinde yeni bir kategori oluşturabilirsiniz:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. Örneğin, website/pages/help.js içinde bir sayfamız varsa, aşağıdakileri ekleyerek ona bağlayabiliriz:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

Harici linkleri yeni bir sekmede açmak için, başlık link yapılandırması içinde bir external: true bayrağı sağlayın.

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

Sitenizde arama etkinleştirilmişse, arama barınız linklerinizin sağında görünür olacak. Linkler ve başlık arasına arama barı koymak isterseniz, headerLinks yapılandırma dizisine bir arama girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

Çeviriler sitenizde etkinleştirilmişse, dil açılır kutusu linklerinizin sağında görünür olacak (ve arama etkinse, arama barının solunda). Linkler ve başlık arasına dil seçimi açılır menüsü koymak isterseniz, headerLinks yapılandırma dizisine bir diller girdisi ekleyin:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/tr/next/publishing.html b/docs/tr/next/publishing.html new file mode 100644 index 0000000000..099849f8a1 --- /dev/null +++ b/docs/tr/next/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

next

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/tr/next/publishing/index.html b/docs/tr/next/publishing/index.html new file mode 100644 index 0000000000..099849f8a1 --- /dev/null +++ b/docs/tr/next/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

next

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/tr/next/search.html b/docs/tr/next/search.html new file mode 100644 index 0000000000..913a84dd4a --- /dev/null +++ b/docs/tr/next/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

next

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/next/search/index.html b/docs/tr/next/search/index.html new file mode 100644 index 0000000000..913a84dd4a --- /dev/null +++ b/docs/tr/next/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

next

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/next/site-config.html b/docs/tr/next/site-config.html new file mode 100644 index 0000000000..c58d0064ff --- /dev/null +++ b/docs/tr/next/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

next

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/next/site-config/index.html b/docs/tr/next/site-config/index.html new file mode 100644 index 0000000000..c58d0064ff --- /dev/null +++ b/docs/tr/next/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

next

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/next/site-creation.html b/docs/tr/next/site-creation.html new file mode 100644 index 0000000000..ef41d0660c --- /dev/null +++ b/docs/tr/next/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

next

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/next/site-creation/index.html b/docs/tr/next/site-creation/index.html new file mode 100644 index 0000000000..ef41d0660c --- /dev/null +++ b/docs/tr/next/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

next

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/next/site-preparation.html b/docs/tr/next/site-preparation.html new file mode 100644 index 0000000000..e955e39df3 --- /dev/null +++ b/docs/tr/next/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

next

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/next/site-preparation/index.html b/docs/tr/next/site-preparation/index.html new file mode 100644 index 0000000000..e955e39df3 --- /dev/null +++ b/docs/tr/next/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

next

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/next/translation.html b/docs/tr/next/translation.html new file mode 100644 index 0000000000..770dd4d40d --- /dev/null +++ b/docs/tr/next/translation.html @@ -0,0 +1,265 @@ +Translations and Localization · Docusaurus

next

Translate

Translations and Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/next/translation/index.html b/docs/tr/next/translation/index.html new file mode 100644 index 0000000000..770dd4d40d --- /dev/null +++ b/docs/tr/next/translation/index.html @@ -0,0 +1,265 @@ +Translations and Localization · Docusaurus

next

Translate

Translations and Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/next/versioning.html b/docs/tr/next/versioning.html new file mode 100644 index 0000000000..154c0b67e3 --- /dev/null +++ b/docs/tr/next/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

next

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/next/versioning/index.html b/docs/tr/next/versioning/index.html new file mode 100644 index 0000000000..154c0b67e3 --- /dev/null +++ b/docs/tr/next/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

next

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/publishing.html b/docs/tr/publishing.html new file mode 100644 index 0000000000..769213253a --- /dev/null +++ b/docs/tr/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/tr/publishing/index.html b/docs/tr/publishing/index.html new file mode 100644 index 0000000000..769213253a --- /dev/null +++ b/docs/tr/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/tr/search.html b/docs/tr/search.html new file mode 100644 index 0000000000..a1f0a080ca --- /dev/null +++ b/docs/tr/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.1

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/search/index.html b/docs/tr/search/index.html new file mode 100644 index 0000000000..a1f0a080ca --- /dev/null +++ b/docs/tr/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.1

Translate

Enabling Search

Docusaurus Algolia DocSearch kullanarak aramayı destekler. Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

Arama Çubuğunu Etkinleştirme

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/tr/site-config.html b/docs/tr/site-config.html new file mode 100644 index 0000000000..c54425dbc7 --- /dev/null +++ b/docs/tr/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.1

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/site-config/index.html b/docs/tr/site-config/index.html new file mode 100644 index 0000000000..c54425dbc7 --- /dev/null +++ b/docs/tr/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.1

Translate

siteConfig.js

Site yapılandırılmasının büyük bir bölümü siteConfig.js dosyasını düzenleyerek yapılıyor.

+

Kullanıcı Vitrini

+

users dizisi sitenizde göstermek istediğiniz her proje/kullanıcı için obje depolamak için kullanılır. Şu anda bu alan pages/en/index.js ve pages/en/users.js dosyalarının sağladığı örnekler için kullanılıyor. Her obje caption, image, infoLink ve pinned alanlarına sahip olmalıdır. The caption is the text showed when someone hovers over the image of that user, and the infoLink is where clicking the image will bring someone. pinned alanı sayfa indeks'inde gösterilip gösterilmeyeceğini belirler.

+

Şu anda bu kullanıcılar dizisi sadece index.js ve users.js örnek dosyaları tarafından kullanılıyor. Eğer kullanıcılar sayfasını istemiyorsanız yada kullanıcıları index sayfasında göstermek istemiyorsanız bu bölümü kaldırabilirsiniz.

+

siteConfig Alanları

+

siteConfig objesi web sitenizin yapılandırma ayarlarını toplu olarak barındırır.

+

Zorunlu Alanlar

+

baseUrl - Siteniz için temel Url.

+

colors - Site için renk yapılandırılması.

+
    +
  • primaryColor başlık gezinme çubuğu ve yan çubuklarda kullanılan renk.
    • +
  • secondaryColor site penceresi daraltığında (mobil de dahil) başlık gezinme çubuğunun ikinci satırında gözüken renk.
    • +
  • Özelleştirilmiş renk yapılandırmaları da eklenebilir. Örnek olarak, eğer $myColor olarak tanımlanmış renklerle birlikte kullanıcı stilleri eklenirse myColor alanına colors eklemek bu rengin kolayca yapılandırılmasını sağlar.
    • +
+

copyright - The copyright string at footer of site and within feed

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

Örnek Kullanım:

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - Boolean. If true, Docusaurus will politely ask crawlers and search engines to avoid indexing your site. This is done with a header tag and so only applies to docs and pages. Will not attempt to hide static resources. This is a best effort request. Malicious crawlers can and will still index your site.

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - Web siteniz için slogan.

+

title - Web siteniz için başlık.

+

url - URL for your website.

+

İsteğe Bağlı Alanlar

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/tr/site-creation.html b/docs/tr/site-creation.html new file mode 100644 index 0000000000..19ce4396fd --- /dev/null +++ b/docs/tr/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/site-creation/index.html b/docs/tr/site-creation/index.html new file mode 100644 index 0000000000..19ce4396fd --- /dev/null +++ b/docs/tr/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

Kurulum ve hazırlıktan sonra dokümanlarınız için basit bir site oluşturma işinin çoğu tamamlanmış olur.

+

Site Yapısı

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Temel Sitenizi Oluşturun

+

Tamamen fonksiyonel bir site oluşturmak için, sadece birkaç adımı yapmanız gerekir:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

Eğer dosyalarınızı sidebars.json dosyasına eklemezseniz, dokümanlar işlenecektir ancak sadece diğer dokümanlara bağlantılanabilirler ve sadece URL biliniyorsa ziyaret edilebilirler.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Değişikliklerinizin sonuçlarını görmek için siteyi çalıştır.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/tr/site-preparation.html b/docs/tr/site-preparation.html new file mode 100644 index 0000000000..945ca63bdc --- /dev/null +++ b/docs/tr/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/site-preparation/index.html b/docs/tr/site-preparation/index.html new file mode 100644 index 0000000000..945ca63bdc --- /dev/null +++ b/docs/tr/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.1

Translate

Site Preparation

After installing Docusaurus, you now have a skeleton to work from for your specific website. The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

+

Directory Structure

+

As shown after you installed Docusaurus, the initialization script created a directory structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js dosyası Docusaurus tarafından üretilen sitenin alt bilgi gibi davranan bir React bileşenidir ve kullanıcı tarafından özelleştirilmelidir.
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js dosyası Docusaurus tarafından kullanılan ana yapılandırma dosyasıdır.
    • +
+

website/siteConfig.js ve website/core/Footer.js dosyalarını sürdürmeniz gerekecek fakat onları istediğiniz gibi düzenleyebilirsiniz.

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. website/pages içerisinde en azından en/index.js yada en/index.html dosyasına ve website/static içerisinde başlık simgeniz olarak kullanılacak bir resme sahip olmalısınız.

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/tr/translation.html b/docs/tr/translation.html new file mode 100644 index 0000000000..8251418dbc --- /dev/null +++ b/docs/tr/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/translation/index.html b/docs/tr/translation/index.html new file mode 100644 index 0000000000..8251418dbc --- /dev/null +++ b/docs/tr/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. İngilizce olarak yazılmış dokümantasyon dosyaları topluluk tarafından çevrilmesi için Crownd'ine yüklenir. İngilizce yazılmış üst seviye sayfalardaki istenilen dizeler <translate> etiketi ile sarılarak çevrilebilir. Diğer başlık ve etiketlerde bulunup uygunca çevrileceklerdir.

+

Docusaurus Tercüme Yapılandırmaları

+

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

+
npm run examples translations
+
+

yada

+
yarn examples translations
+
+

Bu aşağıdaki dosyaları oluşturacaktır:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js dosyası examples komutunun ürettiği aynı başlangıç yardım sayfasına sahiptir ama bu sefer tercüme etiketleri dahildir.
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

Mevcut Dosyalarınız Çevirme

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

Sayfalarda Tercümeyi Etkinleştirme

+

Sayfalar özelleştirilmiş indeks yada yardım sayfaları gibi belirli içerik sayfalarının yada yerleşim düzeninin özelleştirilmesine izin verir.

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

Çevirmek istediğiniz dizeleri <translate> etiketi ile sarın ve dosyanın başına gerekli ifadeyi ekleyin:

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

Aynı zamanda çevirmene dizeleri nasıl çevirmesi gerektiğini söyleyebileceğiniz isteğe bağlı açıklama da ekleyebilirsiniz:

+
<p>
+  <translate desc="çiçek, fiil değil">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

Çevrilecek Dizeleri Toplama

+

Sayfalar içinde bulunan dizeler ayrılmak ve Crowdin'e sağlanmak zorundadırlar.

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

Komutu çalıştırmak İngilizceden diğer dillere çevirilecek her dizeyi barındıran website/i18n/en.json dosyasını oluşturacaktır.

+

Komut aşağıdaki konumlardan metinler içerecektir:

+
    +
  • Dokümanın markdown başlıklarında içerisindeki title ve sidebar_label dizeleri
    • +
  • sidebars.json içerisindeki kategori isimleri
    • +
  • siteConfig.js içerisindeki sloganlar
    • +
  • siteConfig.js içerisindeki başlık bağlantı label dizeleri
    • +
  • pages içerisindeki herhangi bir .js dosyasındaki <translate> etiketi ile sarılmış dizeler
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

Dizeler Nasıl Tercüme Edilir

+

Docusaurus'un kendisi bir dilden başka bir dile çeviri yapmaz. Onun yerine, çevirilecekleri yüklemek ve düzgünce çevirilmişleri indirmek için Crowdin'le etkileşim içindedir.

+

Docusaurus Dize Tercümelerini Nasıl Kullanır

+

Bu bölüm Docusaurus'da tercümelerin nasıl çalıştığı hakkında içerik sağlar.

+

Dizerler

+

Bir Docusaurus sitesi yerelleştirme gerektiren bir çok dizeye sahiptir. Ancak çevirilecek dizelerin listesini tutmak zahmetli olabilir. Docusaurus simplifies this by centralizing strings.

+

Başlık gezintisi, örnek olarak 'Ana Sayfa' yada 'Blog' bağlantılarınıza sahip olabilir. Bu ve sayfalarda bulunan diğer başlık ve kenar çubuğu dizeleri, ayrıştırılmışlardır ve i18n/en.json içerisinde yerleştirilmişlerdir. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Daha sonra, İspanyolca sayfalar oluşturulur, Docusaurus dizelerin İngilizce sürümü ile karşılık gelen, yerelleştirilmiş dizelerin yerini değiştirir. (örn. İspanyolca etkinleştirilmiş sayfalarda 'Yardım' 'Ayuda' olacaktır).

+

Markdown Dosyaları

+

Dokümantasyon sayfalarının kendileri için, tercüme edilmiş dosyalar indirilecek ve daha sonra uygun yerleşim şablonuna göre işlenecekler.

+

Diğer Sayfalar

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. Daha sorunsuz bir tercüme için Crowdin'in rehberleri kullanabilirsiniz. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manüel Olarak Dosya Eşleştirme

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Örnek bir circle.yml dosyası:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin'i yükleme
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # tercüme upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # web sitesini yap ve yayınla
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

crowdin komutu examples komutu ile üretilmiş crowdin.yaml dosyasını kullanır. Dosyaların nasıl yükleneceğini/indirileceğini yapılandırmak için proje dizininizin içerisine yerleştirilmelidir.

+

crowdin.yaml dosyasındaki CROWDIN_PROJECT_ID ve CROWDIN_API_KEY çevresel değişkenlerinin Crowdin projeniz için Daire içerisinde ayarlandığına dikkat edin. Crowdin proje ayarlarında bulunabilirler.

+

Şimdi, Daire web sitenizin kurulumu için öncelikli olarak otomatik şekilde çevirileri almanıza yardımcı olacak. Sağlanan crowdin.yaml dosyası dokümanları website/translated_docs/ içerisine kopyalayacak ve i18n/en.json dizelerinin tercüme edilmiş halini de i18n/${language}.json içerisine kopyalayacak.

+

Eğer sizde Crowdin'i makinenizde yerel olarak kullanmak istiyorsanız Crowdin CLI tool'u yükleyebilir ve circle.yaml dosyasındaki aynı kodu çalıştırabilirsiniz. Tek fark Daire çevresel değişkenlerine sahip olmayacağınız için project_identifier'i ve crowdin.yamldosyası içerisindeki api_key değeri ayarlamak zorundasınız.

+

Sürümlenmiş Tercümeler

+

Eğer sizde dokümanlarınız için tercüme ve sürümleme istiyorsanız crowdin.yaml'ın sonuna aşağıdaki bölümü ekleyin:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Çevrilmiş, sürümlenmiş dokümanlar website/translated_docs/${language}/${version}/ içerisine kopyalanacaklar.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/tr/versioning.html b/docs/tr/versioning.html new file mode 100644 index 0000000000..885716b4f9 --- /dev/null +++ b/docs/tr/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/tr/versioning/index.html b/docs/tr/versioning/index.html new file mode 100644 index 0000000000..885716b4f9 --- /dev/null +++ b/docs/tr/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

Yeni Sürümler Nasıl Oluşturulur

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Sürümleme Modelleri

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Her Sürüm için Dosya Depolama

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Geri Çekme İşlevselliği

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Mevcut Sürümleri Yeniden Adlandırma

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Sürümleme ve Çeviriler

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/api-pages.html b/docs/zh-CN/1.0.11/api-pages.html new file mode 100644 index 0000000000..a774cfe0fc --- /dev/null +++ b/docs/zh-CN/1.0.11/api-pages.html @@ -0,0 +1,175 @@ +Pages and Styles · Docusaurus

1.0.11

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>[Markdown syntax for a link](http://www.example.com)</MarkdownBlock>
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...         
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"  
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p><translate>I like translations</translate></p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">Community</translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require("../../server/translate.js").translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/api-pages/index.html b/docs/zh-CN/1.0.11/api-pages/index.html new file mode 100644 index 0000000000..a774cfe0fc --- /dev/null +++ b/docs/zh-CN/1.0.11/api-pages/index.html @@ -0,0 +1,175 @@ +Pages and Styles · Docusaurus

1.0.11

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>[Markdown syntax for a link](http://www.example.com)</MarkdownBlock>
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...         
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"  
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p><translate>I like translations</translate></p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">Community</translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require("../../server/translate.js").translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/blog.html b/docs/zh-CN/1.0.11/blog.html new file mode 100644 index 0000000000..e1524d28b7 --- /dev/null +++ b/docs/zh-CN/1.0.11/blog.html @@ -0,0 +1,129 @@ +Adding a Blog · Docusaurus

1.0.11

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipusm..
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The url associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook ID that is used to extract the profile picture.
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/blog/index.html b/docs/zh-CN/1.0.11/blog/index.html new file mode 100644 index 0000000000..e1524d28b7 --- /dev/null +++ b/docs/zh-CN/1.0.11/blog/index.html @@ -0,0 +1,129 @@ +Adding a Blog · Docusaurus

1.0.11

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipusm..
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The url associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook ID that is used to extract the profile picture.
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/commands.html b/docs/zh-CN/1.0.11/commands.html new file mode 100644 index 0000000000..6b3b10cf5f --- /dev/null +++ b/docs/zh-CN/1.0.11/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.11

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/commands/index.html b/docs/zh-CN/1.0.11/commands/index.html new file mode 100644 index 0000000000..6b3b10cf5f --- /dev/null +++ b/docs/zh-CN/1.0.11/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.11

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/custom-pages.html b/docs/zh-CN/1.0.11/custom-pages.html new file mode 100644 index 0000000000..a52714e9eb --- /dev/null +++ b/docs/zh-CN/1.0.11/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.11

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/custom-pages/index.html b/docs/zh-CN/1.0.11/custom-pages/index.html new file mode 100644 index 0000000000..a52714e9eb --- /dev/null +++ b/docs/zh-CN/1.0.11/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.11

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/doc-markdown.html b/docs/zh-CN/1.0.11/doc-markdown.html new file mode 100644 index 0000000000..d862e3bcb0 --- /dev/null +++ b/docs/zh-CN/1.0.11/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.11

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/doc-markdown/index.html b/docs/zh-CN/1.0.11/doc-markdown/index.html new file mode 100644 index 0000000000..d862e3bcb0 --- /dev/null +++ b/docs/zh-CN/1.0.11/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.11

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/installation.html b/docs/zh-CN/1.0.11/installation.html new file mode 100644 index 0000000000..50e1af631b --- /dev/null +++ b/docs/zh-CN/1.0.11/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.11

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

验证安装

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/installation/index.html b/docs/zh-CN/1.0.11/installation/index.html new file mode 100644 index 0000000000..50e1af631b --- /dev/null +++ b/docs/zh-CN/1.0.11/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.11

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

验证安装

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/navigation.html b/docs/zh-CN/1.0.11/navigation.html new file mode 100644 index 0000000000..b69f1ab733 --- /dev/null +++ b/docs/zh-CN/1.0.11/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.11

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/navigation/index.html b/docs/zh-CN/1.0.11/navigation/index.html new file mode 100644 index 0000000000..b69f1ab733 --- /dev/null +++ b/docs/zh-CN/1.0.11/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.11

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/publishing.html b/docs/zh-CN/1.0.11/publishing.html new file mode 100644 index 0000000000..94ffac1f1a --- /dev/null +++ b/docs/zh-CN/1.0.11/publishing.html @@ -0,0 +1,185 @@ +Publishing your site · Docusaurus

1.0.11

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's "html" directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+
    +
  • organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
    • +
  • projectName: The name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
    • +
+
+

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.

+

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:

+
    +
  • GIT_USER: The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
    • +
+

There are also two optional parameters that are set as environment variables:

+
    +

  • USE_SSH: If this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.

    • +

  • CURRENT_BRANCH: The branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.

    • +
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master   
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/publishing/index.html b/docs/zh-CN/1.0.11/publishing/index.html new file mode 100644 index 0000000000..94ffac1f1a --- /dev/null +++ b/docs/zh-CN/1.0.11/publishing/index.html @@ -0,0 +1,185 @@ +Publishing your site · Docusaurus

1.0.11

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's "html" directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+
    +
  • organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
    • +
  • projectName: The name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
    • +
+
+

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.

+

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:

+
    +
  • GIT_USER: The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
    • +
+

There are also two optional parameters that are set as environment variables:

+
    +

  • USE_SSH: If this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.

    • +

  • CURRENT_BRANCH: The branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.

    • +
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master   
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/search.html b/docs/zh-CN/1.0.11/search.html new file mode 100644 index 0000000000..5f6bb83396 --- /dev/null +++ b/docs/zh-CN/1.0.11/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.11

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/search/index.html b/docs/zh-CN/1.0.11/search/index.html new file mode 100644 index 0000000000..5f6bb83396 --- /dev/null +++ b/docs/zh-CN/1.0.11/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.11

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/site-config.html b/docs/zh-CN/1.0.11/site-config.html new file mode 100644 index 0000000000..a45cf05960 --- /dev/null +++ b/docs/zh-CN/1.0.11/site-config.html @@ -0,0 +1,231 @@ +siteConfig.js · Docusaurus

1.0.11

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - url for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - url for an Open Graph image. This image will show up when your site is shared on Facebook, Twitter and any other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - url for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with all fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+// For github.io type URLS, you would combine the url and baseUrl like:
+// url: "https://reasonml.github.io",
+// baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+// For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+// users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true"
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/site-config/index.html b/docs/zh-CN/1.0.11/site-config/index.html new file mode 100644 index 0000000000..a45cf05960 --- /dev/null +++ b/docs/zh-CN/1.0.11/site-config/index.html @@ -0,0 +1,231 @@ +siteConfig.js · Docusaurus

1.0.11

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - url for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - url for an Open Graph image. This image will show up when your site is shared on Facebook, Twitter and any other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - url for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with all fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+// For github.io type URLS, you would combine the url and baseUrl like:
+// url: "https://reasonml.github.io",
+// baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+// For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+// users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true"
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/site-creation.html b/docs/zh-CN/1.0.11/site-creation.html new file mode 100644 index 0000000000..6244743da8 --- /dev/null +++ b/docs/zh-CN/1.0.11/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.11

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/site-creation/index.html b/docs/zh-CN/1.0.11/site-creation/index.html new file mode 100644 index 0000000000..6244743da8 --- /dev/null +++ b/docs/zh-CN/1.0.11/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.11

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/site-preparation.html b/docs/zh-CN/1.0.11/site-preparation.html new file mode 100644 index 0000000000..ff76cc4558 --- /dev/null +++ b/docs/zh-CN/1.0.11/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.11

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/site-preparation/index.html b/docs/zh-CN/1.0.11/site-preparation/index.html new file mode 100644 index 0000000000..ff76cc4558 --- /dev/null +++ b/docs/zh-CN/1.0.11/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.11

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/translation.html b/docs/zh-CN/1.0.11/translation.html new file mode 100644 index 0000000000..1a145fa9b4 --- /dev/null +++ b/docs/zh-CN/1.0.11/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.11

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/translation/index.html b/docs/zh-CN/1.0.11/translation/index.html new file mode 100644 index 0000000000..1a145fa9b4 --- /dev/null +++ b/docs/zh-CN/1.0.11/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.11

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/versioning.html b/docs/zh-CN/1.0.11/versioning.html new file mode 100644 index 0000000000..c31e198bec --- /dev/null +++ b/docs/zh-CN/1.0.11/versioning.html @@ -0,0 +1,108 @@ +Versioning · Docusaurus

1.0.11

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.11/versioning/index.html b/docs/zh-CN/1.0.11/versioning/index.html new file mode 100644 index 0000000000..c31e198bec --- /dev/null +++ b/docs/zh-CN/1.0.11/versioning/index.html @@ -0,0 +1,108 @@ +Versioning · Docusaurus

1.0.11

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/api-pages.html b/docs/zh-CN/1.0.12/api-pages.html new file mode 100644 index 0000000000..b7dc46a1c6 --- /dev/null +++ b/docs/zh-CN/1.0.12/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.12

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/api-pages/index.html b/docs/zh-CN/1.0.12/api-pages/index.html new file mode 100644 index 0000000000..b7dc46a1c6 --- /dev/null +++ b/docs/zh-CN/1.0.12/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.12

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/blog.html b/docs/zh-CN/1.0.12/blog.html new file mode 100644 index 0000000000..e4740dd2fd --- /dev/null +++ b/docs/zh-CN/1.0.12/blog.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.12

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/blog/index.html b/docs/zh-CN/1.0.12/blog/index.html new file mode 100644 index 0000000000..e4740dd2fd --- /dev/null +++ b/docs/zh-CN/1.0.12/blog/index.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.12

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/commands.html b/docs/zh-CN/1.0.12/commands.html new file mode 100644 index 0000000000..c9e976a690 --- /dev/null +++ b/docs/zh-CN/1.0.12/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.12

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/commands/index.html b/docs/zh-CN/1.0.12/commands/index.html new file mode 100644 index 0000000000..c9e976a690 --- /dev/null +++ b/docs/zh-CN/1.0.12/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.12

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/custom-pages.html b/docs/zh-CN/1.0.12/custom-pages.html new file mode 100644 index 0000000000..f69894b69f --- /dev/null +++ b/docs/zh-CN/1.0.12/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.12

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/custom-pages/index.html b/docs/zh-CN/1.0.12/custom-pages/index.html new file mode 100644 index 0000000000..f69894b69f --- /dev/null +++ b/docs/zh-CN/1.0.12/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.12

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/doc-markdown.html b/docs/zh-CN/1.0.12/doc-markdown.html new file mode 100644 index 0000000000..1baa579b90 --- /dev/null +++ b/docs/zh-CN/1.0.12/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.12

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/doc-markdown/index.html b/docs/zh-CN/1.0.12/doc-markdown/index.html new file mode 100644 index 0000000000..1baa579b90 --- /dev/null +++ b/docs/zh-CN/1.0.12/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.12

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/installation.html b/docs/zh-CN/1.0.12/installation.html new file mode 100644 index 0000000000..251e8c01e8 --- /dev/null +++ b/docs/zh-CN/1.0.12/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.12

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

验证安装

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/installation/index.html b/docs/zh-CN/1.0.12/installation/index.html new file mode 100644 index 0000000000..251e8c01e8 --- /dev/null +++ b/docs/zh-CN/1.0.12/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.12

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

验证安装

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/navigation.html b/docs/zh-CN/1.0.12/navigation.html new file mode 100644 index 0000000000..f9cada3518 --- /dev/null +++ b/docs/zh-CN/1.0.12/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.12

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/navigation/index.html b/docs/zh-CN/1.0.12/navigation/index.html new file mode 100644 index 0000000000..f9cada3518 --- /dev/null +++ b/docs/zh-CN/1.0.12/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.12

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/publishing.html b/docs/zh-CN/1.0.12/publishing.html new file mode 100644 index 0000000000..11a0c4bbb9 --- /dev/null +++ b/docs/zh-CN/1.0.12/publishing.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.12

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/publishing/index.html b/docs/zh-CN/1.0.12/publishing/index.html new file mode 100644 index 0000000000..11a0c4bbb9 --- /dev/null +++ b/docs/zh-CN/1.0.12/publishing/index.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.12

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/search.html b/docs/zh-CN/1.0.12/search.html new file mode 100644 index 0000000000..e45bf4a5eb --- /dev/null +++ b/docs/zh-CN/1.0.12/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.12

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/search/index.html b/docs/zh-CN/1.0.12/search/index.html new file mode 100644 index 0000000000..e45bf4a5eb --- /dev/null +++ b/docs/zh-CN/1.0.12/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.12

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/site-config.html b/docs/zh-CN/1.0.12/site-config.html new file mode 100644 index 0000000000..9cf1d5c630 --- /dev/null +++ b/docs/zh-CN/1.0.12/site-config.html @@ -0,0 +1,234 @@ +siteConfig.js · Docusaurus

1.0.12

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/site-config/index.html b/docs/zh-CN/1.0.12/site-config/index.html new file mode 100644 index 0000000000..9cf1d5c630 --- /dev/null +++ b/docs/zh-CN/1.0.12/site-config/index.html @@ -0,0 +1,234 @@ +siteConfig.js · Docusaurus

1.0.12

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/site-creation.html b/docs/zh-CN/1.0.12/site-creation.html new file mode 100644 index 0000000000..e33df1a911 --- /dev/null +++ b/docs/zh-CN/1.0.12/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.12

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/site-creation/index.html b/docs/zh-CN/1.0.12/site-creation/index.html new file mode 100644 index 0000000000..e33df1a911 --- /dev/null +++ b/docs/zh-CN/1.0.12/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.12

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/site-preparation.html b/docs/zh-CN/1.0.12/site-preparation.html new file mode 100644 index 0000000000..6312da3c28 --- /dev/null +++ b/docs/zh-CN/1.0.12/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.12

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/site-preparation/index.html b/docs/zh-CN/1.0.12/site-preparation/index.html new file mode 100644 index 0000000000..6312da3c28 --- /dev/null +++ b/docs/zh-CN/1.0.12/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.12

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/translation.html b/docs/zh-CN/1.0.12/translation.html new file mode 100644 index 0000000000..39725a83bd --- /dev/null +++ b/docs/zh-CN/1.0.12/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.12

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/translation/index.html b/docs/zh-CN/1.0.12/translation/index.html new file mode 100644 index 0000000000..39725a83bd --- /dev/null +++ b/docs/zh-CN/1.0.12/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.12

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/versioning.html b/docs/zh-CN/1.0.12/versioning.html new file mode 100644 index 0000000000..8fc1f9eaf2 --- /dev/null +++ b/docs/zh-CN/1.0.12/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.12

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.12/versioning/index.html b/docs/zh-CN/1.0.12/versioning/index.html new file mode 100644 index 0000000000..8fc1f9eaf2 --- /dev/null +++ b/docs/zh-CN/1.0.12/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.12

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/api-pages.html b/docs/zh-CN/1.0.13/api-pages.html new file mode 100644 index 0000000000..c5eb620c9b --- /dev/null +++ b/docs/zh-CN/1.0.13/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.13

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/api-pages/index.html b/docs/zh-CN/1.0.13/api-pages/index.html new file mode 100644 index 0000000000..c5eb620c9b --- /dev/null +++ b/docs/zh-CN/1.0.13/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.13

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/blog.html b/docs/zh-CN/1.0.13/blog.html new file mode 100644 index 0000000000..eba7109a2e --- /dev/null +++ b/docs/zh-CN/1.0.13/blog.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.13

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/blog/index.html b/docs/zh-CN/1.0.13/blog/index.html new file mode 100644 index 0000000000..eba7109a2e --- /dev/null +++ b/docs/zh-CN/1.0.13/blog/index.html @@ -0,0 +1,130 @@ +Adding a Blog · Docusaurus

1.0.13

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/commands.html b/docs/zh-CN/1.0.13/commands.html new file mode 100644 index 0000000000..5bcdb3599a --- /dev/null +++ b/docs/zh-CN/1.0.13/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.13

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/commands/index.html b/docs/zh-CN/1.0.13/commands/index.html new file mode 100644 index 0000000000..5bcdb3599a --- /dev/null +++ b/docs/zh-CN/1.0.13/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.13

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/custom-pages.html b/docs/zh-CN/1.0.13/custom-pages.html new file mode 100644 index 0000000000..dafa3acd1e --- /dev/null +++ b/docs/zh-CN/1.0.13/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.13

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/custom-pages/index.html b/docs/zh-CN/1.0.13/custom-pages/index.html new file mode 100644 index 0000000000..dafa3acd1e --- /dev/null +++ b/docs/zh-CN/1.0.13/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.13

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/doc-markdown.html b/docs/zh-CN/1.0.13/doc-markdown.html new file mode 100644 index 0000000000..780bd21acd --- /dev/null +++ b/docs/zh-CN/1.0.13/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.13

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/doc-markdown/index.html b/docs/zh-CN/1.0.13/doc-markdown/index.html new file mode 100644 index 0000000000..780bd21acd --- /dev/null +++ b/docs/zh-CN/1.0.13/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.13

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/installation.html b/docs/zh-CN/1.0.13/installation.html new file mode 100644 index 0000000000..5bc3e7601c --- /dev/null +++ b/docs/zh-CN/1.0.13/installation.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.13

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

验证安装

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/installation/index.html b/docs/zh-CN/1.0.13/installation/index.html new file mode 100644 index 0000000000..5bc3e7601c --- /dev/null +++ b/docs/zh-CN/1.0.13/installation/index.html @@ -0,0 +1,110 @@ +Installation · Docusaurus

1.0.13

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. yarn global add docusaurus-init or npm install --global docusaurus-init

    4. +

  4. docusaurus-init

    5. +
+
+

After docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing npm list docusaurus. You can update to the latest version of Docusaurus by typing npm update.

+
+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

If you do not want to install the init script globally, you can install it locally and then run it via npx docusaurus-init or from the node_modules directory that is created via ./node_modules/.bin/docusaurus-init. You may want to remove the created package.json file and node_modules directory after you run the script.

+
+

验证安装

+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/navigation.html b/docs/zh-CN/1.0.13/navigation.html new file mode 100644 index 0000000000..0fa9eb0a7b --- /dev/null +++ b/docs/zh-CN/1.0.13/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.13

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/navigation/index.html b/docs/zh-CN/1.0.13/navigation/index.html new file mode 100644 index 0000000000..0fa9eb0a7b --- /dev/null +++ b/docs/zh-CN/1.0.13/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.13

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/publishing.html b/docs/zh-CN/1.0.13/publishing.html new file mode 100644 index 0000000000..235c883d31 --- /dev/null +++ b/docs/zh-CN/1.0.13/publishing.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.13

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/publishing/index.html b/docs/zh-CN/1.0.13/publishing/index.html new file mode 100644 index 0000000000..235c883d31 --- /dev/null +++ b/docs/zh-CN/1.0.13/publishing/index.html @@ -0,0 +1,200 @@ +Publishing your site · Docusaurus

1.0.13

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/search.html b/docs/zh-CN/1.0.13/search.html new file mode 100644 index 0000000000..0d973bda64 --- /dev/null +++ b/docs/zh-CN/1.0.13/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.13

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/search/index.html b/docs/zh-CN/1.0.13/search/index.html new file mode 100644 index 0000000000..0d973bda64 --- /dev/null +++ b/docs/zh-CN/1.0.13/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.13

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/site-config.html b/docs/zh-CN/1.0.13/site-config.html new file mode 100644 index 0000000000..d484b89f1a --- /dev/null +++ b/docs/zh-CN/1.0.13/site-config.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.13

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/site-config/index.html b/docs/zh-CN/1.0.13/site-config/index.html new file mode 100644 index 0000000000..d484b89f1a --- /dev/null +++ b/docs/zh-CN/1.0.13/site-config/index.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.13

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/site-creation.html b/docs/zh-CN/1.0.13/site-creation.html new file mode 100644 index 0000000000..a58ccd857b --- /dev/null +++ b/docs/zh-CN/1.0.13/site-creation.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.13

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/site-creation/index.html b/docs/zh-CN/1.0.13/site-creation/index.html new file mode 100644 index 0000000000..a58ccd857b --- /dev/null +++ b/docs/zh-CN/1.0.13/site-creation/index.html @@ -0,0 +1,110 @@ +Creating your site · Docusaurus

1.0.13

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
    7. +
+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/site-preparation.html b/docs/zh-CN/1.0.13/site-preparation.html new file mode 100644 index 0000000000..9720343011 --- /dev/null +++ b/docs/zh-CN/1.0.13/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.13

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/site-preparation/index.html b/docs/zh-CN/1.0.13/site-preparation/index.html new file mode 100644 index 0000000000..9720343011 --- /dev/null +++ b/docs/zh-CN/1.0.13/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.13

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/translation.html b/docs/zh-CN/1.0.13/translation.html new file mode 100644 index 0000000000..77414f8fe4 --- /dev/null +++ b/docs/zh-CN/1.0.13/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.13

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/translation/index.html b/docs/zh-CN/1.0.13/translation/index.html new file mode 100644 index 0000000000..77414f8fe4 --- /dev/null +++ b/docs/zh-CN/1.0.13/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.13

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/versioning.html b/docs/zh-CN/1.0.13/versioning.html new file mode 100644 index 0000000000..2463b06dd8 --- /dev/null +++ b/docs/zh-CN/1.0.13/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.13

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.13/versioning/index.html b/docs/zh-CN/1.0.13/versioning/index.html new file mode 100644 index 0000000000..2463b06dd8 --- /dev/null +++ b/docs/zh-CN/1.0.13/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.13

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/api-pages.html b/docs/zh-CN/1.0.14/api-pages.html new file mode 100644 index 0000000000..13105fb4b3 --- /dev/null +++ b/docs/zh-CN/1.0.14/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.14

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/api-pages/index.html b/docs/zh-CN/1.0.14/api-pages/index.html new file mode 100644 index 0000000000..13105fb4b3 --- /dev/null +++ b/docs/zh-CN/1.0.14/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.14

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

Urls for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to "../../core/CompLibrary.js" to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path "../core/CompLibrary.js".

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, "process.cwd() + /core/mycomponent.js".

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding "static". For example, if the site's baseUrl is "/docusaurus/", an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/blog.html b/docs/zh-CN/1.0.14/blog.html new file mode 100644 index 0000000000..43a16be1b7 --- /dev/null +++ b/docs/zh-CN/1.0.14/blog.html @@ -0,0 +1,191 @@ +Adding a Blog · Docusaurus

1.0.14

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. +

    + Create a file index.html in website/static/. +

    +
    2. +
    <li>
+  <p>
+    Place the contents of the template below into <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Delete the dynamic landing page <code>website/pages/en/index.js</code>
+  </p>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+

+ 

<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=blog/">
+        <script type="text/javascript">
+            window.location.href = "blog/"
+        </script>
+        <title>Title of Your Blog</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='blog/'>link</a>.
+    </body>
+</html>
+

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/blog/index.html b/docs/zh-CN/1.0.14/blog/index.html new file mode 100644 index 0000000000..43a16be1b7 --- /dev/null +++ b/docs/zh-CN/1.0.14/blog/index.html @@ -0,0 +1,191 @@ +Adding a Blog · Docusaurus

1.0.14

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    {blog: true, label: 'Blog'},
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. +

    + Create a file index.html in website/static/. +

    +
    2. +
    <li>
+  <p>
+    Place the contents of the template below into <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+  </p>
+</li>
+
+<li>
+  <p>
+    Delete the dynamic landing page <code>website/pages/en/index.js</code>
+  </p>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+

+ 

<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=blog/">
+        <script type="text/javascript">
+            window.location.href = "blog/"
+        </script>
+        <title>Title of Your Blog</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='blog/'>link</a>.
+    </body>
+</html>
+

← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/commands.html b/docs/zh-CN/1.0.14/commands.html new file mode 100644 index 0000000000..0aac6be3b6 --- /dev/null +++ b/docs/zh-CN/1.0.14/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.14

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/commands/index.html b/docs/zh-CN/1.0.14/commands/index.html new file mode 100644 index 0000000000..0aac6be3b6 --- /dev/null +++ b/docs/zh-CN/1.0.14/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.14

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/custom-pages.html b/docs/zh-CN/1.0.14/custom-pages.html new file mode 100644 index 0000000000..cf976c0e48 --- /dev/null +++ b/docs/zh-CN/1.0.14/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.14

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/custom-pages/index.html b/docs/zh-CN/1.0.14/custom-pages/index.html new file mode 100644 index 0000000000..cf976c0e48 --- /dev/null +++ b/docs/zh-CN/1.0.14/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.14

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│       └── index.js
+│       └── users.js
+│       └── help.js
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: "about-slash", label: "About/"},

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require("react");
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/doc-markdown.html b/docs/zh-CN/1.0.14/doc-markdown.html new file mode 100644 index 0000000000..87179055c9 --- /dev/null +++ b/docs/zh-CN/1.0.14/doc-markdown.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.14

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/doc-markdown/index.html b/docs/zh-CN/1.0.14/doc-markdown/index.html new file mode 100644 index 0000000000..87179055c9 --- /dev/null +++ b/docs/zh-CN/1.0.14/doc-markdown/index.html @@ -0,0 +1,172 @@ +Markdown Features · Docusaurus

1.0.14

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```javascript
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
highlight: {
+  theme: 'default'
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
highlight: {
+  theme: 'default',
+  hljs: function(hljs) {
+    hljs.registerLanguage('galacticbasic', function(hljs) {
+      // ...
+    });
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/installation.html b/docs/zh-CN/1.0.14/installation.html new file mode 100644 index 0000000000..9ed485407b --- /dev/null +++ b/docs/zh-CN/1.0.14/installation.html @@ -0,0 +1,106 @@ +Installation · Docusaurus

1.0.14

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init > If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    4. +
+
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/installation/index.html b/docs/zh-CN/1.0.14/installation/index.html new file mode 100644 index 0000000000..9ed485407b --- /dev/null +++ b/docs/zh-CN/1.0.14/installation/index.html @@ -0,0 +1,106 @@ +Installation · Docusaurus

1.0.14

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure setup for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init > If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    4. +
+
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/navigation.html b/docs/zh-CN/1.0.14/navigation.html new file mode 100644 index 0000000000..1492c4672b --- /dev/null +++ b/docs/zh-CN/1.0.14/navigation.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.14

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/navigation/index.html b/docs/zh-CN/1.0.14/navigation/index.html new file mode 100644 index 0000000000..1492c4672b --- /dev/null +++ b/docs/zh-CN/1.0.14/navigation/index.html @@ -0,0 +1,187 @@ +Navigation and Sidebars · Docusaurus

1.0.14

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flatfile structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My *new content* here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    ...
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+  },
+  ...
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+  ...
+  { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
headerLinks: [
+  ...
+  { 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: [
+  ...
+  { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { search: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
headerLinks: [
+  { doc: 'foo', label: 'Foo' },
+  { languages: true },
+  { doc: 'bar', label: 'Bar' },
+],
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
onPageNav: 'separate',
+
+

Currently, separate is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/publishing.html b/docs/zh-CN/1.0.14/publishing.html new file mode 100644 index 0000000000..482dae6d67 --- /dev/null +++ b/docs/zh-CN/1.0.14/publishing.html @@ -0,0 +1,221 @@ +Publishing your site · Docusaurus

1.0.14

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +
  1. Select New site from Git
    2. +
  2. Connect to your preferred Git provider.
    3. +
  3. Select the branch to deploy. Default is master
    4. +
  4. Configure your build steps:
    5. +
+
    +
  • For your build command enter: cd website; npm install; npm run build;
    • +
  • For publish directory: build/<projectName> (use the projectName from your siteConfig)
    • +
+
    +
  1. Click Deploy site
    2. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/publishing/index.html b/docs/zh-CN/1.0.14/publishing/index.html new file mode 100644 index 0000000000..482dae6d67 --- /dev/null +++ b/docs/zh-CN/1.0.14/publishing/index.html @@ -0,0 +1,221 @@ +Publishing your site · Docusaurus

1.0.14

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +
  1. Select New site from Git
    2. +
  2. Connect to your preferred Git provider.
    3. +
  3. Select the branch to deploy. Default is master
    4. +
  4. Configure your build steps:
    5. +
+
    +
  • For your build command enter: cd website; npm install; npm run build;
    • +
  • For publish directory: build/<projectName> (use the projectName from your siteConfig)
    • +
+
    +
  1. Click Deploy site
    2. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/search.html b/docs/zh-CN/1.0.14/search.html new file mode 100644 index 0000000000..4846abbb40 --- /dev/null +++ b/docs/zh-CN/1.0.14/search.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.14

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/search/index.html b/docs/zh-CN/1.0.14/search/index.html new file mode 100644 index 0000000000..4846abbb40 --- /dev/null +++ b/docs/zh-CN/1.0.14/search/index.html @@ -0,0 +1,106 @@ +Enabling Search · Docusaurus

1.0.14

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once you have set up your site, enter your site information to have Algolia crawl your website's documentation pages. Algolia will then send you an API key and index name for your site.

+

启用搜索框

+

Enter your search-only API key and index name into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: "my-search-only-api-key-1234",
+    indexName: "my-index-name"
+  },
+  ...
+}
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {
+  ...
+  algolia: {
+    ...
+    algoliaOptions: {
+      facetFilters: [ "tags:VERSION" ],
+      hitsPerPage: 5
+    }
+  },
+}
+
+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar in between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+}
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/site-config.html b/docs/zh-CN/1.0.14/site-config.html new file mode 100644 index 0000000000..fa93620006 --- /dev/null +++ b/docs/zh-CN/1.0.14/site-config.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.14

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/site-config/index.html b/docs/zh-CN/1.0.14/site-config/index.html new file mode 100644 index 0000000000..fa93620006 --- /dev/null +++ b/docs/zh-CN/1.0.14/site-config/index.html @@ -0,0 +1,235 @@ +siteConfig.js · Docusaurus

1.0.14

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: "docs/site"
+
+
customDocsPath: "website-docs"
+
+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    "Times New Roman",
+    "Serif"
+  ],
+  myOtherFont: [
+    "-apple-system",
+    "system-ui"
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: "User1",
+    image: "/test-site/img/docusaurus.svg",
+    infoLink: "https://www.example.com",
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: "Docusaurus",
+  tagline: "Generate websites!",
+  url: "https://docusaurus.io",
+  baseUrl: "/",
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: "https://reasonml.github.io",
+  // baseUrl: "/reason-react/",
+  organizationName: "facebook",
+  projectName: "docusaurus",
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: "doc1", label: "Docs" },
+    { page: "help", label: "Help" },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: "img/docusaurus.svg",
+  favicon: "img/favicon.png",
+  colors: {
+    primaryColor: "#2E8555",
+    secondaryColor: "#205C3B"
+  },
+  editUrl: "https://github.com/facebook/docusaurus/edit/master/docs/",
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ["static/css/non-docusaurus", "static/assets/separate-css"],
+  footerIcon: "img/docusaurus.svg",
+  translationRecruitingLink:
+    "https://crowdin.com/project/docusaurus",
+  algolia: {
+    apiKey:
+      "0f9f28b9ab9efae89810921a351753b5",
+    indexName: "github"
+  },
+  gaTrackingId: "U-A2352",
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ "https://docusaurus.io/slash.js" ],
+  stylesheets: [ "https://docusaurus.io/style.css" ],
+  facebookAppId: "1615782811974223",
+  facebookPixelId: "352490515235776",
+  twitter: "true",
+  twitterImage: "img/docusaurus.png",
+  ogImage: "img/docusaurus.png",
+};
+
+module.exports = siteConfig;
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/site-creation.html b/docs/zh-CN/1.0.14/site-creation.html new file mode 100644 index 0000000000..c9d835f4e5 --- /dev/null +++ b/docs/zh-CN/1.0.14/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.14

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+        <script type="text/javascript">
+            window.location.href = "docs/id-of-doc-to-land-on.html"
+        </script>
+        <title>Your Site Title Here</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='docs/id-of-doc-to-land-on.html'>link</a>.
+    </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/site-creation/index.html b/docs/zh-CN/1.0.14/site-creation/index.html new file mode 100644 index 0000000000..c9d835f4e5 --- /dev/null +++ b/docs/zh-CN/1.0.14/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.14

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+└── website
+│   └── blog
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
     ---
+ id: intro
+ title: Getting Started
+ ---
+ 
+ My *new content* here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
     cd website
+ yarn run start # or `npm run start`
+ # navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+    <head>
+        <meta charset="UTF-8">
+        <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+        <script type="text/javascript">
+            window.location.href = "docs/id-of-doc-to-land-on.html"
+        </script>
+        <title>Your Site Title Here</title>
+    </head>
+    <body>
+        If you are not redirected automatically, follow this <a href='docs/id-of-doc-to-land-on.html'>link</a>.
+    </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/site-preparation.html b/docs/zh-CN/1.0.14/site-preparation.html new file mode 100644 index 0000000000..2935659878 --- /dev/null +++ b/docs/zh-CN/1.0.14/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.14

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/site-preparation/index.html b/docs/zh-CN/1.0.14/site-preparation/index.html new file mode 100644 index 0000000000..2935659878 --- /dev/null +++ b/docs/zh-CN/1.0.14/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.14

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   └── doc1.md
+│   └── doc2.md
+│   └── doc3.md
+│   └── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+│   └── blog-examples-from-docusaurus
+│       └── 2016-03-11-blog-post.md
+│       └── 2017-04-10-blog-post-two.md
+│   └── core
+│       └── Footer.js
+│   └── node_modules
+│   └── package.json
+│   └── pages
+│   └── sidebars.json
+│   └── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/translation.html b/docs/zh-CN/1.0.14/translation.html new file mode 100644 index 0000000000..765858deb0 --- /dev/null +++ b/docs/zh-CN/1.0.14/translation.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.14

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/translation/index.html b/docs/zh-CN/1.0.14/translation/index.html new file mode 100644 index 0000000000..765858deb0 --- /dev/null +++ b/docs/zh-CN/1.0.14/translation/index.html @@ -0,0 +1,237 @@ +Translations & Localization · Docusaurus

1.0.14

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require("../../server/translate.js").translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
...
+"scripts": {
+  "write-translations": "docusaurus-write-translations"
+},
+...
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/versioning.html b/docs/zh-CN/1.0.14/versioning.html new file mode 100644 index 0000000000..09712f697e --- /dev/null +++ b/docs/zh-CN/1.0.14/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.14

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.14/versioning/index.html b/docs/zh-CN/1.0.14/versioning/index.html new file mode 100644 index 0000000000..09712f697e --- /dev/null +++ b/docs/zh-CN/1.0.14/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.14

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/api-pages.html b/docs/zh-CN/1.0.15/api-pages.html new file mode 100644 index 0000000000..5d00fe1cbd --- /dev/null +++ b/docs/zh-CN/1.0.15/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.15

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/api-pages/index.html b/docs/zh-CN/1.0.15/api-pages/index.html new file mode 100644 index 0000000000..5d00fe1cbd --- /dev/null +++ b/docs/zh-CN/1.0.15/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.0.15

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/blog.html b/docs/zh-CN/1.0.15/blog.html new file mode 100644 index 0000000000..c35a14d60b --- /dev/null +++ b/docs/zh-CN/1.0.15/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.0.15

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/blog/index.html b/docs/zh-CN/1.0.15/blog/index.html new file mode 100644 index 0000000000..c35a14d60b --- /dev/null +++ b/docs/zh-CN/1.0.15/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.0.15

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/commands.html b/docs/zh-CN/1.0.15/commands.html new file mode 100644 index 0000000000..00a281b050 --- /dev/null +++ b/docs/zh-CN/1.0.15/commands.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.15

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/commands/index.html b/docs/zh-CN/1.0.15/commands/index.html new file mode 100644 index 0000000000..00a281b050 --- /dev/null +++ b/docs/zh-CN/1.0.15/commands/index.html @@ -0,0 +1,139 @@ +CLI Commands · Docusaurus

1.0.15

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples [feature]

+

别名：examples

+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    e.g.,

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version <currentVersion> <newVersion>

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+

See the Versioning guide to learn more.

+
+

docusaurus-start [--port <number>]

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.

+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/custom-pages.html b/docs/zh-CN/1.0.15/custom-pages.html new file mode 100644 index 0000000000..2c75b6462e --- /dev/null +++ b/docs/zh-CN/1.0.15/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.15

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/custom-pages/index.html b/docs/zh-CN/1.0.15/custom-pages/index.html new file mode 100644 index 0000000000..2c75b6462e --- /dev/null +++ b/docs/zh-CN/1.0.15/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.0.15

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/doc-markdown.html b/docs/zh-CN/1.0.15/doc-markdown.html new file mode 100644 index 0000000000..49a6cc4065 --- /dev/null +++ b/docs/zh-CN/1.0.15/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.0.15

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/doc-markdown/index.html b/docs/zh-CN/1.0.15/doc-markdown/index.html new file mode 100644 index 0000000000..49a6cc4065 --- /dev/null +++ b/docs/zh-CN/1.0.15/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.0.15

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/installation.html b/docs/zh-CN/1.0.15/installation.html new file mode 100644 index 0000000000..f3599857a9 --- /dev/null +++ b/docs/zh-CN/1.0.15/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.0.15

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/installation/index.html b/docs/zh-CN/1.0.15/installation/index.html new file mode 100644 index 0000000000..f3599857a9 --- /dev/null +++ b/docs/zh-CN/1.0.15/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.0.15

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/navigation.html b/docs/zh-CN/1.0.15/navigation.html new file mode 100644 index 0000000000..d42b3a2f8f --- /dev/null +++ b/docs/zh-CN/1.0.15/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.0.15

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/navigation/index.html b/docs/zh-CN/1.0.15/navigation/index.html new file mode 100644 index 0000000000..d42b3a2f8f --- /dev/null +++ b/docs/zh-CN/1.0.15/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.0.15

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/publishing.html b/docs/zh-CN/1.0.15/publishing.html new file mode 100644 index 0000000000..50e383e92a --- /dev/null +++ b/docs/zh-CN/1.0.15/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.0.15

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/publishing/index.html b/docs/zh-CN/1.0.15/publishing/index.html new file mode 100644 index 0000000000..50e383e92a --- /dev/null +++ b/docs/zh-CN/1.0.15/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.0.15

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only one circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:7.10
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/search.html b/docs/zh-CN/1.0.15/search.html new file mode 100644 index 0000000000..4bfbd95284 --- /dev/null +++ b/docs/zh-CN/1.0.15/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.0.15

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/search/index.html b/docs/zh-CN/1.0.15/search/index.html new file mode 100644 index 0000000000..4bfbd95284 --- /dev/null +++ b/docs/zh-CN/1.0.15/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.0.15

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/site-config.html b/docs/zh-CN/1.0.15/site-config.html new file mode 100644 index 0000000000..b214997b2a --- /dev/null +++ b/docs/zh-CN/1.0.15/site-config.html @@ -0,0 +1,239 @@ +siteConfig.js · Docusaurus

1.0.15

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site'
+
+
customDocsPath: 'website-docs'
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: 'doc1', label: 'Docs' },
+    { page: 'help', label: 'Help' },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B'
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink:
+    'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey:
+      '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github'
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ 'https://docusaurus.io/slash.js' ],
+  stylesheets: [ 'https://docusaurus.io/style.css' ],
+  facebookAppId: '1615782811974223',
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/site-config/index.html b/docs/zh-CN/1.0.15/site-config/index.html new file mode 100644 index 0000000000..b214997b2a --- /dev/null +++ b/docs/zh-CN/1.0.15/site-config/index.html @@ -0,0 +1,239 @@ +siteConfig.js · Docusaurus

1.0.15

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site'
+
+
customDocsPath: 'website-docs'
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons at the bottom of your blog posts, provide a Facebook application id, and the buttons will show up on all blog posts.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true
+  }
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    { doc: 'doc1', label: 'Docs' },
+    { page: 'help', label: 'Help' },
+    { search: true },
+    { blog: true }
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B'
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink:
+    'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey:
+      '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github'
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default'
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(tokens, idx, options, env, instance) {
+        return '<div class="foo">bar</div>';
+      }
+    }
+  ],
+  scripts: [ 'https://docusaurus.io/slash.js' ],
+  stylesheets: [ 'https://docusaurus.io/style.css' ],
+  facebookAppId: '1615782811974223',
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/site-creation.html b/docs/zh-CN/1.0.15/site-creation.html new file mode 100644 index 0000000000..939affa3bf --- /dev/null +++ b/docs/zh-CN/1.0.15/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.15

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/site-creation/index.html b/docs/zh-CN/1.0.15/site-creation/index.html new file mode 100644 index 0000000000..939affa3bf --- /dev/null +++ b/docs/zh-CN/1.0.15/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.0.15

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/site-preparation.html b/docs/zh-CN/1.0.15/site-preparation.html new file mode 100644 index 0000000000..64057adad0 --- /dev/null +++ b/docs/zh-CN/1.0.15/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.15

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/site-preparation/index.html b/docs/zh-CN/1.0.15/site-preparation/index.html new file mode 100644 index 0000000000..64057adad0 --- /dev/null +++ b/docs/zh-CN/1.0.15/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.0.15

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/translation.html b/docs/zh-CN/1.0.15/translation.html new file mode 100644 index 0000000000..d1d7b0dfec --- /dev/null +++ b/docs/zh-CN/1.0.15/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.0.15

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/translation/index.html b/docs/zh-CN/1.0.15/translation/index.html new file mode 100644 index 0000000000..d1d7b0dfec --- /dev/null +++ b/docs/zh-CN/1.0.15/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.0.15

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/versioning.html b/docs/zh-CN/1.0.15/versioning.html new file mode 100644 index 0000000000..69cd1d22ed --- /dev/null +++ b/docs/zh-CN/1.0.15/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.15

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.0.15/versioning/index.html b/docs/zh-CN/1.0.15/versioning/index.html new file mode 100644 index 0000000000..69cd1d22ed --- /dev/null +++ b/docs/zh-CN/1.0.15/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.0.15

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/api-pages.html b/docs/zh-CN/1.1.0/api-pages.html new file mode 100644 index 0000000000..17f32f7458 --- /dev/null +++ b/docs/zh-CN/1.1.0/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.0

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/api-pages/index.html b/docs/zh-CN/1.1.0/api-pages/index.html new file mode 100644 index 0000000000..17f32f7458 --- /dev/null +++ b/docs/zh-CN/1.1.0/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.0

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/blog.html b/docs/zh-CN/1.1.0/blog.html new file mode 100644 index 0000000000..e60e83382c --- /dev/null +++ b/docs/zh-CN/1.1.0/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.0

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/blog/index.html b/docs/zh-CN/1.1.0/blog/index.html new file mode 100644 index 0000000000..e60e83382c --- /dev/null +++ b/docs/zh-CN/1.1.0/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.0

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/commands.html b/docs/zh-CN/1.1.0/commands.html new file mode 100644 index 0000000000..512cec22de --- /dev/null +++ b/docs/zh-CN/1.1.0/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.0

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/commands/index.html b/docs/zh-CN/1.1.0/commands/index.html new file mode 100644 index 0000000000..512cec22de --- /dev/null +++ b/docs/zh-CN/1.1.0/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.0

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/custom-pages.html b/docs/zh-CN/1.1.0/custom-pages.html new file mode 100644 index 0000000000..b68ea52aec --- /dev/null +++ b/docs/zh-CN/1.1.0/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/custom-pages/index.html b/docs/zh-CN/1.1.0/custom-pages/index.html new file mode 100644 index 0000000000..b68ea52aec --- /dev/null +++ b/docs/zh-CN/1.1.0/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/doc-markdown.html b/docs/zh-CN/1.1.0/doc-markdown.html new file mode 100644 index 0000000000..2d3611353c --- /dev/null +++ b/docs/zh-CN/1.1.0/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.0

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/doc-markdown/index.html b/docs/zh-CN/1.1.0/doc-markdown/index.html new file mode 100644 index 0000000000..2d3611353c --- /dev/null +++ b/docs/zh-CN/1.1.0/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.0

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/installation.html b/docs/zh-CN/1.1.0/installation.html new file mode 100644 index 0000000000..3abcd7c072 --- /dev/null +++ b/docs/zh-CN/1.1.0/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.0

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/installation/index.html b/docs/zh-CN/1.1.0/installation/index.html new file mode 100644 index 0000000000..3abcd7c072 --- /dev/null +++ b/docs/zh-CN/1.1.0/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.0

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/navigation.html b/docs/zh-CN/1.1.0/navigation.html new file mode 100644 index 0000000000..5d642a113b --- /dev/null +++ b/docs/zh-CN/1.1.0/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/navigation/index.html b/docs/zh-CN/1.1.0/navigation/index.html new file mode 100644 index 0000000000..5d642a113b --- /dev/null +++ b/docs/zh-CN/1.1.0/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/publishing.html b/docs/zh-CN/1.1.0/publishing.html new file mode 100644 index 0000000000..1fd4f0bd24 --- /dev/null +++ b/docs/zh-CN/1.1.0/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/publishing/index.html b/docs/zh-CN/1.1.0/publishing/index.html new file mode 100644 index 0000000000..1fd4f0bd24 --- /dev/null +++ b/docs/zh-CN/1.1.0/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/search.html b/docs/zh-CN/1.1.0/search.html new file mode 100644 index 0000000000..7eaae6a96e --- /dev/null +++ b/docs/zh-CN/1.1.0/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.0

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/search/index.html b/docs/zh-CN/1.1.0/search/index.html new file mode 100644 index 0000000000..7eaae6a96e --- /dev/null +++ b/docs/zh-CN/1.1.0/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.0

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/site-config.html b/docs/zh-CN/1.1.0/site-config.html new file mode 100644 index 0000000000..245a0eaf5a --- /dev/null +++ b/docs/zh-CN/1.1.0/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.0

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/site-config/index.html b/docs/zh-CN/1.1.0/site-config/index.html new file mode 100644 index 0000000000..245a0eaf5a --- /dev/null +++ b/docs/zh-CN/1.1.0/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.0

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/site-creation.html b/docs/zh-CN/1.1.0/site-creation.html new file mode 100644 index 0000000000..24ae9bfa60 --- /dev/null +++ b/docs/zh-CN/1.1.0/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/site-creation/index.html b/docs/zh-CN/1.1.0/site-creation/index.html new file mode 100644 index 0000000000..24ae9bfa60 --- /dev/null +++ b/docs/zh-CN/1.1.0/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/site-preparation.html b/docs/zh-CN/1.1.0/site-preparation.html new file mode 100644 index 0000000000..44e5e159f5 --- /dev/null +++ b/docs/zh-CN/1.1.0/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.0

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/site-preparation/index.html b/docs/zh-CN/1.1.0/site-preparation/index.html new file mode 100644 index 0000000000..44e5e159f5 --- /dev/null +++ b/docs/zh-CN/1.1.0/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.0

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/translation.html b/docs/zh-CN/1.1.0/translation.html new file mode 100644 index 0000000000..38958d9620 --- /dev/null +++ b/docs/zh-CN/1.1.0/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/translation/index.html b/docs/zh-CN/1.1.0/translation/index.html new file mode 100644 index 0000000000..38958d9620 --- /dev/null +++ b/docs/zh-CN/1.1.0/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/versioning.html b/docs/zh-CN/1.1.0/versioning.html new file mode 100644 index 0000000000..01f3ba938c --- /dev/null +++ b/docs/zh-CN/1.1.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.0

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.0/versioning/index.html b/docs/zh-CN/1.1.0/versioning/index.html new file mode 100644 index 0000000000..01f3ba938c --- /dev/null +++ b/docs/zh-CN/1.1.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.0

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/api-pages.html b/docs/zh-CN/1.1.1/api-pages.html new file mode 100644 index 0000000000..7cd54de687 --- /dev/null +++ b/docs/zh-CN/1.1.1/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.1

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/api-pages/index.html b/docs/zh-CN/1.1.1/api-pages/index.html new file mode 100644 index 0000000000..7cd54de687 --- /dev/null +++ b/docs/zh-CN/1.1.1/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.1

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/blog.html b/docs/zh-CN/1.1.1/blog.html new file mode 100644 index 0000000000..c162be388d --- /dev/null +++ b/docs/zh-CN/1.1.1/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.1

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/blog/index.html b/docs/zh-CN/1.1.1/blog/index.html new file mode 100644 index 0000000000..c162be388d --- /dev/null +++ b/docs/zh-CN/1.1.1/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.1

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/commands.html b/docs/zh-CN/1.1.1/commands.html new file mode 100644 index 0000000000..79ae08c1b7 --- /dev/null +++ b/docs/zh-CN/1.1.1/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.1

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/commands/index.html b/docs/zh-CN/1.1.1/commands/index.html new file mode 100644 index 0000000000..79ae08c1b7 --- /dev/null +++ b/docs/zh-CN/1.1.1/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.1

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/custom-pages.html b/docs/zh-CN/1.1.1/custom-pages.html new file mode 100644 index 0000000000..d71793dbab --- /dev/null +++ b/docs/zh-CN/1.1.1/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/custom-pages/index.html b/docs/zh-CN/1.1.1/custom-pages/index.html new file mode 100644 index 0000000000..d71793dbab --- /dev/null +++ b/docs/zh-CN/1.1.1/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/doc-markdown.html b/docs/zh-CN/1.1.1/doc-markdown.html new file mode 100644 index 0000000000..9b36960b78 --- /dev/null +++ b/docs/zh-CN/1.1.1/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.1

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/doc-markdown/index.html b/docs/zh-CN/1.1.1/doc-markdown/index.html new file mode 100644 index 0000000000..9b36960b78 --- /dev/null +++ b/docs/zh-CN/1.1.1/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.1

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/installation.html b/docs/zh-CN/1.1.1/installation.html new file mode 100644 index 0000000000..c8f382278d --- /dev/null +++ b/docs/zh-CN/1.1.1/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.1

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/installation/index.html b/docs/zh-CN/1.1.1/installation/index.html new file mode 100644 index 0000000000..c8f382278d --- /dev/null +++ b/docs/zh-CN/1.1.1/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.1

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/navigation.html b/docs/zh-CN/1.1.1/navigation.html new file mode 100644 index 0000000000..1c39c773f3 --- /dev/null +++ b/docs/zh-CN/1.1.1/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/navigation/index.html b/docs/zh-CN/1.1.1/navigation/index.html new file mode 100644 index 0000000000..1c39c773f3 --- /dev/null +++ b/docs/zh-CN/1.1.1/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/publishing.html b/docs/zh-CN/1.1.1/publishing.html new file mode 100644 index 0000000000..47038145c9 --- /dev/null +++ b/docs/zh-CN/1.1.1/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/publishing/index.html b/docs/zh-CN/1.1.1/publishing/index.html new file mode 100644 index 0000000000..47038145c9 --- /dev/null +++ b/docs/zh-CN/1.1.1/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/search.html b/docs/zh-CN/1.1.1/search.html new file mode 100644 index 0000000000..d624ac0cc4 --- /dev/null +++ b/docs/zh-CN/1.1.1/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.1

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/search/index.html b/docs/zh-CN/1.1.1/search/index.html new file mode 100644 index 0000000000..d624ac0cc4 --- /dev/null +++ b/docs/zh-CN/1.1.1/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.1

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/site-config.html b/docs/zh-CN/1.1.1/site-config.html new file mode 100644 index 0000000000..623fe2cdfe --- /dev/null +++ b/docs/zh-CN/1.1.1/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.1

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/site-config/index.html b/docs/zh-CN/1.1.1/site-config/index.html new file mode 100644 index 0000000000..623fe2cdfe --- /dev/null +++ b/docs/zh-CN/1.1.1/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.1

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/site-creation.html b/docs/zh-CN/1.1.1/site-creation.html new file mode 100644 index 0000000000..6b5769163a --- /dev/null +++ b/docs/zh-CN/1.1.1/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/site-creation/index.html b/docs/zh-CN/1.1.1/site-creation/index.html new file mode 100644 index 0000000000..6b5769163a --- /dev/null +++ b/docs/zh-CN/1.1.1/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/site-preparation.html b/docs/zh-CN/1.1.1/site-preparation.html new file mode 100644 index 0000000000..e91dd726b7 --- /dev/null +++ b/docs/zh-CN/1.1.1/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.1

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/site-preparation/index.html b/docs/zh-CN/1.1.1/site-preparation/index.html new file mode 100644 index 0000000000..e91dd726b7 --- /dev/null +++ b/docs/zh-CN/1.1.1/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.1

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/translation.html b/docs/zh-CN/1.1.1/translation.html new file mode 100644 index 0000000000..f1668d872c --- /dev/null +++ b/docs/zh-CN/1.1.1/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/translation/index.html b/docs/zh-CN/1.1.1/translation/index.html new file mode 100644 index 0000000000..f1668d872c --- /dev/null +++ b/docs/zh-CN/1.1.1/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/versioning.html b/docs/zh-CN/1.1.1/versioning.html new file mode 100644 index 0000000000..dedc5cde60 --- /dev/null +++ b/docs/zh-CN/1.1.1/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.1

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.1/versioning/index.html b/docs/zh-CN/1.1.1/versioning/index.html new file mode 100644 index 0000000000..dedc5cde60 --- /dev/null +++ b/docs/zh-CN/1.1.1/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.1

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/api-pages.html b/docs/zh-CN/1.1.2/api-pages.html new file mode 100644 index 0000000000..8f351dc019 --- /dev/null +++ b/docs/zh-CN/1.1.2/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.2

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/api-pages/index.html b/docs/zh-CN/1.1.2/api-pages/index.html new file mode 100644 index 0000000000..8f351dc019 --- /dev/null +++ b/docs/zh-CN/1.1.2/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.2

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/blog.html b/docs/zh-CN/1.1.2/blog.html new file mode 100644 index 0000000000..ed786a4ff4 --- /dev/null +++ b/docs/zh-CN/1.1.2/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.2

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/blog/index.html b/docs/zh-CN/1.1.2/blog/index.html new file mode 100644 index 0000000000..ed786a4ff4 --- /dev/null +++ b/docs/zh-CN/1.1.2/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.2

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/commands.html b/docs/zh-CN/1.1.2/commands.html new file mode 100644 index 0000000000..acc1dc01c4 --- /dev/null +++ b/docs/zh-CN/1.1.2/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.2

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/commands/index.html b/docs/zh-CN/1.1.2/commands/index.html new file mode 100644 index 0000000000..acc1dc01c4 --- /dev/null +++ b/docs/zh-CN/1.1.2/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.2

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/custom-pages.html b/docs/zh-CN/1.1.2/custom-pages.html new file mode 100644 index 0000000000..9d0d477ef7 --- /dev/null +++ b/docs/zh-CN/1.1.2/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.2

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/custom-pages/index.html b/docs/zh-CN/1.1.2/custom-pages/index.html new file mode 100644 index 0000000000..9d0d477ef7 --- /dev/null +++ b/docs/zh-CN/1.1.2/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.2

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/doc-markdown.html b/docs/zh-CN/1.1.2/doc-markdown.html new file mode 100644 index 0000000000..3360f20f25 --- /dev/null +++ b/docs/zh-CN/1.1.2/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.2

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/doc-markdown/index.html b/docs/zh-CN/1.1.2/doc-markdown/index.html new file mode 100644 index 0000000000..3360f20f25 --- /dev/null +++ b/docs/zh-CN/1.1.2/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.2

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/installation.html b/docs/zh-CN/1.1.2/installation.html new file mode 100644 index 0000000000..3a3466bc97 --- /dev/null +++ b/docs/zh-CN/1.1.2/installation.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.2

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/installation/index.html b/docs/zh-CN/1.1.2/installation/index.html new file mode 100644 index 0000000000..3a3466bc97 --- /dev/null +++ b/docs/zh-CN/1.1.2/installation/index.html @@ -0,0 +1,107 @@ +Installation · Docusaurus

1.1.2

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/navigation.html b/docs/zh-CN/1.1.2/navigation.html new file mode 100644 index 0000000000..b1dce1aefe --- /dev/null +++ b/docs/zh-CN/1.1.2/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.2

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/navigation/index.html b/docs/zh-CN/1.1.2/navigation/index.html new file mode 100644 index 0000000000..b1dce1aefe --- /dev/null +++ b/docs/zh-CN/1.1.2/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.2

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/publishing.html b/docs/zh-CN/1.1.2/publishing.html new file mode 100644 index 0000000000..d5dfd1651b --- /dev/null +++ b/docs/zh-CN/1.1.2/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.2

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/publishing/index.html b/docs/zh-CN/1.1.2/publishing/index.html new file mode 100644 index 0000000000..d5dfd1651b --- /dev/null +++ b/docs/zh-CN/1.1.2/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.2

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/search.html b/docs/zh-CN/1.1.2/search.html new file mode 100644 index 0000000000..abd7fef766 --- /dev/null +++ b/docs/zh-CN/1.1.2/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.2

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/search/index.html b/docs/zh-CN/1.1.2/search/index.html new file mode 100644 index 0000000000..abd7fef766 --- /dev/null +++ b/docs/zh-CN/1.1.2/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.2

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/site-config.html b/docs/zh-CN/1.1.2/site-config.html new file mode 100644 index 0000000000..9154ab37b9 --- /dev/null +++ b/docs/zh-CN/1.1.2/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.2

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/site-config/index.html b/docs/zh-CN/1.1.2/site-config/index.html new file mode 100644 index 0000000000..9154ab37b9 --- /dev/null +++ b/docs/zh-CN/1.1.2/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.2

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/site-creation.html b/docs/zh-CN/1.1.2/site-creation.html new file mode 100644 index 0000000000..a39086eea7 --- /dev/null +++ b/docs/zh-CN/1.1.2/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.2

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/site-creation/index.html b/docs/zh-CN/1.1.2/site-creation/index.html new file mode 100644 index 0000000000..a39086eea7 --- /dev/null +++ b/docs/zh-CN/1.1.2/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.2

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/site-preparation.html b/docs/zh-CN/1.1.2/site-preparation.html new file mode 100644 index 0000000000..31c8af6b5c --- /dev/null +++ b/docs/zh-CN/1.1.2/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.2

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/site-preparation/index.html b/docs/zh-CN/1.1.2/site-preparation/index.html new file mode 100644 index 0000000000..31c8af6b5c --- /dev/null +++ b/docs/zh-CN/1.1.2/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.2

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/translation.html b/docs/zh-CN/1.1.2/translation.html new file mode 100644 index 0000000000..200d634919 --- /dev/null +++ b/docs/zh-CN/1.1.2/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.2

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/translation/index.html b/docs/zh-CN/1.1.2/translation/index.html new file mode 100644 index 0000000000..200d634919 --- /dev/null +++ b/docs/zh-CN/1.1.2/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.2

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/versioning.html b/docs/zh-CN/1.1.2/versioning.html new file mode 100644 index 0000000000..708eac6871 --- /dev/null +++ b/docs/zh-CN/1.1.2/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.2

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.2/versioning/index.html b/docs/zh-CN/1.1.2/versioning/index.html new file mode 100644 index 0000000000..708eac6871 --- /dev/null +++ b/docs/zh-CN/1.1.2/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.2

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/api-pages.html b/docs/zh-CN/1.1.3/api-pages.html new file mode 100644 index 0000000000..3728d549ed --- /dev/null +++ b/docs/zh-CN/1.1.3/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.3

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/api-pages/index.html b/docs/zh-CN/1.1.3/api-pages/index.html new file mode 100644 index 0000000000..3728d549ed --- /dev/null +++ b/docs/zh-CN/1.1.3/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.3

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/blog.html b/docs/zh-CN/1.1.3/blog.html new file mode 100644 index 0000000000..2300389c4d --- /dev/null +++ b/docs/zh-CN/1.1.3/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.3

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/blog/index.html b/docs/zh-CN/1.1.3/blog/index.html new file mode 100644 index 0000000000..2300389c4d --- /dev/null +++ b/docs/zh-CN/1.1.3/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.3

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/commands.html b/docs/zh-CN/1.1.3/commands.html new file mode 100644 index 0000000000..dc0a6b8a8b --- /dev/null +++ b/docs/zh-CN/1.1.3/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.3

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/commands/index.html b/docs/zh-CN/1.1.3/commands/index.html new file mode 100644 index 0000000000..dc0a6b8a8b --- /dev/null +++ b/docs/zh-CN/1.1.3/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.3

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/custom-pages.html b/docs/zh-CN/1.1.3/custom-pages.html new file mode 100644 index 0000000000..2a27888ecb --- /dev/null +++ b/docs/zh-CN/1.1.3/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.3

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/custom-pages/index.html b/docs/zh-CN/1.1.3/custom-pages/index.html new file mode 100644 index 0000000000..2a27888ecb --- /dev/null +++ b/docs/zh-CN/1.1.3/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.3

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/doc-markdown.html b/docs/zh-CN/1.1.3/doc-markdown.html new file mode 100644 index 0000000000..09f83b7433 --- /dev/null +++ b/docs/zh-CN/1.1.3/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.3

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/doc-markdown/index.html b/docs/zh-CN/1.1.3/doc-markdown/index.html new file mode 100644 index 0000000000..09f83b7433 --- /dev/null +++ b/docs/zh-CN/1.1.3/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.3

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/installation.html b/docs/zh-CN/1.1.3/installation.html new file mode 100644 index 0000000000..a012480566 --- /dev/null +++ b/docs/zh-CN/1.1.3/installation.html @@ -0,0 +1,112 @@ +Installation · Docusaurus

1.1.3

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   └── 2017-04-10-blog-post-two.md
+    ├── core
+    │   └── Footer.js
+    ├── node_modules
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/installation/index.html b/docs/zh-CN/1.1.3/installation/index.html new file mode 100644 index 0000000000..a012480566 --- /dev/null +++ b/docs/zh-CN/1.1.3/installation/index.html @@ -0,0 +1,112 @@ +Installation · Docusaurus

1.1.3

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   └── 2017-04-10-blog-post-two.md
+    ├── core
+    │   └── Footer.js
+    ├── node_modules
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/navigation.html b/docs/zh-CN/1.1.3/navigation.html new file mode 100644 index 0000000000..204a19825f --- /dev/null +++ b/docs/zh-CN/1.1.3/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.3

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/navigation/index.html b/docs/zh-CN/1.1.3/navigation/index.html new file mode 100644 index 0000000000..204a19825f --- /dev/null +++ b/docs/zh-CN/1.1.3/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.3

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/publishing.html b/docs/zh-CN/1.1.3/publishing.html new file mode 100644 index 0000000000..fece433bbe --- /dev/null +++ b/docs/zh-CN/1.1.3/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.3

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/publishing/index.html b/docs/zh-CN/1.1.3/publishing/index.html new file mode 100644 index 0000000000..fece433bbe --- /dev/null +++ b/docs/zh-CN/1.1.3/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.3

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/search.html b/docs/zh-CN/1.1.3/search.html new file mode 100644 index 0000000000..d47e4d549d --- /dev/null +++ b/docs/zh-CN/1.1.3/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.3

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/search/index.html b/docs/zh-CN/1.1.3/search/index.html new file mode 100644 index 0000000000..d47e4d549d --- /dev/null +++ b/docs/zh-CN/1.1.3/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.3

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/site-config.html b/docs/zh-CN/1.1.3/site-config.html new file mode 100644 index 0000000000..c602aaabcd --- /dev/null +++ b/docs/zh-CN/1.1.3/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.3

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/site-config/index.html b/docs/zh-CN/1.1.3/site-config/index.html new file mode 100644 index 0000000000..c602aaabcd --- /dev/null +++ b/docs/zh-CN/1.1.3/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.3

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/site-creation.html b/docs/zh-CN/1.1.3/site-creation.html new file mode 100644 index 0000000000..79812bc0f6 --- /dev/null +++ b/docs/zh-CN/1.1.3/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.3

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/site-creation/index.html b/docs/zh-CN/1.1.3/site-creation/index.html new file mode 100644 index 0000000000..79812bc0f6 --- /dev/null +++ b/docs/zh-CN/1.1.3/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.3

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/site-preparation.html b/docs/zh-CN/1.1.3/site-preparation.html new file mode 100644 index 0000000000..099ac428b4 --- /dev/null +++ b/docs/zh-CN/1.1.3/site-preparation.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.3

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/site-preparation/index.html b/docs/zh-CN/1.1.3/site-preparation/index.html new file mode 100644 index 0000000000..099ac428b4 --- /dev/null +++ b/docs/zh-CN/1.1.3/site-preparation/index.html @@ -0,0 +1,99 @@ +Site Preparation · Docusaurus

1.1.3

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-of-repo
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+├── website
+│   ├── blog-examples-from-docusaurus
+│   │   ├── 2016-03-11-blog-post.md
+│   │   └── 2017-04-10-blog-post-two.md
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/translation.html b/docs/zh-CN/1.1.3/translation.html new file mode 100644 index 0000000000..b6050ebf15 --- /dev/null +++ b/docs/zh-CN/1.1.3/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.3

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/translation/index.html b/docs/zh-CN/1.1.3/translation/index.html new file mode 100644 index 0000000000..b6050ebf15 --- /dev/null +++ b/docs/zh-CN/1.1.3/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.3

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/versioning.html b/docs/zh-CN/1.1.3/versioning.html new file mode 100644 index 0000000000..54be68b9e5 --- /dev/null +++ b/docs/zh-CN/1.1.3/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.3

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.3/versioning/index.html b/docs/zh-CN/1.1.3/versioning/index.html new file mode 100644 index 0000000000..54be68b9e5 --- /dev/null +++ b/docs/zh-CN/1.1.3/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.3

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/api-pages.html b/docs/zh-CN/1.1.4/api-pages.html new file mode 100644 index 0000000000..6a4675cfca --- /dev/null +++ b/docs/zh-CN/1.1.4/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.4

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/api-pages/index.html b/docs/zh-CN/1.1.4/api-pages/index.html new file mode 100644 index 0000000000..6a4675cfca --- /dev/null +++ b/docs/zh-CN/1.1.4/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.4

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/blog.html b/docs/zh-CN/1.1.4/blog.html new file mode 100644 index 0000000000..7a3f1a7c76 --- /dev/null +++ b/docs/zh-CN/1.1.4/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.4

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/blog/index.html b/docs/zh-CN/1.1.4/blog/index.html new file mode 100644 index 0000000000..7a3f1a7c76 --- /dev/null +++ b/docs/zh-CN/1.1.4/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.4

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/commands.html b/docs/zh-CN/1.1.4/commands.html new file mode 100644 index 0000000000..82038539f7 --- /dev/null +++ b/docs/zh-CN/1.1.4/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.4

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/commands/index.html b/docs/zh-CN/1.1.4/commands/index.html new file mode 100644 index 0000000000..82038539f7 --- /dev/null +++ b/docs/zh-CN/1.1.4/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.4

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/custom-pages.html b/docs/zh-CN/1.1.4/custom-pages.html new file mode 100644 index 0000000000..6df4d7f633 --- /dev/null +++ b/docs/zh-CN/1.1.4/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.4

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/custom-pages/index.html b/docs/zh-CN/1.1.4/custom-pages/index.html new file mode 100644 index 0000000000..6df4d7f633 --- /dev/null +++ b/docs/zh-CN/1.1.4/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.4

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/doc-markdown.html b/docs/zh-CN/1.1.4/doc-markdown.html new file mode 100644 index 0000000000..cd4bb068f0 --- /dev/null +++ b/docs/zh-CN/1.1.4/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.4

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/doc-markdown/index.html b/docs/zh-CN/1.1.4/doc-markdown/index.html new file mode 100644 index 0000000000..cd4bb068f0 --- /dev/null +++ b/docs/zh-CN/1.1.4/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.4

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/installation.html b/docs/zh-CN/1.1.4/installation.html new file mode 100644 index 0000000000..8d4eb3a203 --- /dev/null +++ b/docs/zh-CN/1.1.4/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.4

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/installation/index.html b/docs/zh-CN/1.1.4/installation/index.html new file mode 100644 index 0000000000..8d4eb3a203 --- /dev/null +++ b/docs/zh-CN/1.1.4/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.4

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/navigation.html b/docs/zh-CN/1.1.4/navigation.html new file mode 100644 index 0000000000..39a41b327d --- /dev/null +++ b/docs/zh-CN/1.1.4/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.4

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/navigation/index.html b/docs/zh-CN/1.1.4/navigation/index.html new file mode 100644 index 0000000000..39a41b327d --- /dev/null +++ b/docs/zh-CN/1.1.4/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.4

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/publishing.html b/docs/zh-CN/1.1.4/publishing.html new file mode 100644 index 0000000000..ebd2f1117d --- /dev/null +++ b/docs/zh-CN/1.1.4/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.4

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/publishing/index.html b/docs/zh-CN/1.1.4/publishing/index.html new file mode 100644 index 0000000000..ebd2f1117d --- /dev/null +++ b/docs/zh-CN/1.1.4/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.4

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/search.html b/docs/zh-CN/1.1.4/search.html new file mode 100644 index 0000000000..9043ba0558 --- /dev/null +++ b/docs/zh-CN/1.1.4/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.4

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/search/index.html b/docs/zh-CN/1.1.4/search/index.html new file mode 100644 index 0000000000..9043ba0558 --- /dev/null +++ b/docs/zh-CN/1.1.4/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.4

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/site-config.html b/docs/zh-CN/1.1.4/site-config.html new file mode 100644 index 0000000000..5f25191b65 --- /dev/null +++ b/docs/zh-CN/1.1.4/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.4

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/site-config/index.html b/docs/zh-CN/1.1.4/site-config/index.html new file mode 100644 index 0000000000..5f25191b65 --- /dev/null +++ b/docs/zh-CN/1.1.4/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.4

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/site-creation.html b/docs/zh-CN/1.1.4/site-creation.html new file mode 100644 index 0000000000..f911c47677 --- /dev/null +++ b/docs/zh-CN/1.1.4/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.4

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/site-creation/index.html b/docs/zh-CN/1.1.4/site-creation/index.html new file mode 100644 index 0000000000..f911c47677 --- /dev/null +++ b/docs/zh-CN/1.1.4/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.4

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/site-preparation.html b/docs/zh-CN/1.1.4/site-preparation.html new file mode 100644 index 0000000000..81ffc312c5 --- /dev/null +++ b/docs/zh-CN/1.1.4/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.4

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/site-preparation/index.html b/docs/zh-CN/1.1.4/site-preparation/index.html new file mode 100644 index 0000000000..81ffc312c5 --- /dev/null +++ b/docs/zh-CN/1.1.4/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.4

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/translation.html b/docs/zh-CN/1.1.4/translation.html new file mode 100644 index 0000000000..cfd7ed5904 --- /dev/null +++ b/docs/zh-CN/1.1.4/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.4

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/translation/index.html b/docs/zh-CN/1.1.4/translation/index.html new file mode 100644 index 0000000000..cfd7ed5904 --- /dev/null +++ b/docs/zh-CN/1.1.4/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.4

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/versioning.html b/docs/zh-CN/1.1.4/versioning.html new file mode 100644 index 0000000000..f03266f68d --- /dev/null +++ b/docs/zh-CN/1.1.4/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.4

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.4/versioning/index.html b/docs/zh-CN/1.1.4/versioning/index.html new file mode 100644 index 0000000000..f03266f68d --- /dev/null +++ b/docs/zh-CN/1.1.4/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.4

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/api-pages.html b/docs/zh-CN/1.1.5/api-pages.html new file mode 100644 index 0000000000..f242841aea --- /dev/null +++ b/docs/zh-CN/1.1.5/api-pages.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.5

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/api-pages/index.html b/docs/zh-CN/1.1.5/api-pages/index.html new file mode 100644 index 0000000000..f242841aea --- /dev/null +++ b/docs/zh-CN/1.1.5/api-pages/index.html @@ -0,0 +1,181 @@ +Pages and Styles · Docusaurus

1.1.5

Translate

Pages and Styles

Docusaurus支持在website/pages文件夹内将页面编写为React组件，该文件夹将会和网站的其他部分共享相同的页眉，页脚和样式。

+

URLs for Pages

+

任何在website/pages文件夹中的.js文件都将会使用文件路径中"pages"之后的部分渲染成静态html。 website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 例如：website/pages/en/help.js中的页面可以通过${baseUrl}en/help.js或${baseUrl}help.js来访问，其中的 ${baseUrl}就是siteConfig.js 文件中设置的baseUrl字段。

+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages folder are temporarily copied into node_modules/docusaurus when rendering to static html. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website folder, use process.cwd() which will refer to the website folder to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repo for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. Urls for non-English pages will use their language tags as specified in the languages.js file. E.g. The url for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static folder. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static folder. Any .css files you provide in the static folder will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/blog.html b/docs/zh-CN/1.1.5/blog.html new file mode 100644 index 0000000000..1be66e3981 --- /dev/null +++ b/docs/zh-CN/1.1.5/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.5

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/blog/index.html b/docs/zh-CN/1.1.5/blog/index.html new file mode 100644 index 0000000000..1be66e3981 --- /dev/null +++ b/docs/zh-CN/1.1.5/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.1.5

Translate

Adding a Blog

初始设置

+

要设置你的网站博客，需在你的工程website目录下先创建一个blog目录。

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog folder with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

在播客文章中使用 <!--truncate--> 标记，这样，在浏览全部已发布的文章时，就可以看到博客中各文章的摘要信息。 <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

可用的选项是一个整数或字符串'ALL'，表示您希望显示的文章数量。

+

例如：

+
blogSidebarCount: 'ALL'
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main folder. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/commands.html b/docs/zh-CN/1.1.5/commands.html new file mode 100644 index 0000000000..9f9a25cf48 --- /dev/null +++ b/docs/zh-CN/1.1.5/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.5

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/commands/index.html b/docs/zh-CN/1.1.5/commands/index.html new file mode 100644 index 0000000000..9f9a25cf48 --- /dev/null +++ b/docs/zh-CN/1.1.5/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.1.5

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +

  • GIT_USER: 与部署提交联系的 GIT 用户。

    • +

  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.

    +

    Example

    +
    GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
    • +
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/custom-pages.html b/docs/zh-CN/1.1.5/custom-pages.html new file mode 100644 index 0000000000..9850c66ff1 --- /dev/null +++ b/docs/zh-CN/1.1.5/custom-pages.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.5

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/custom-pages/index.html b/docs/zh-CN/1.1.5/custom-pages/index.html new file mode 100644 index 0000000000..9850c66ff1 --- /dev/null +++ b/docs/zh-CN/1.1.5/custom-pages/index.html @@ -0,0 +1,111 @@ +Custom Pages · Docusaurus

1.1.5

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   │   ├── index.js
+│   │   ├── users.js
+│   │   └── help.js
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static folder in the same way as other static assets. 或者，它们也可以被放置在pages文件夹中，并以原本方式发送给客户端，而不会被React渲染。

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static html pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/doc-markdown.html b/docs/zh-CN/1.1.5/doc-markdown.html new file mode 100644 index 0000000000..12250424c1 --- /dev/null +++ b/docs/zh-CN/1.1.5/doc-markdown.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.5

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/doc-markdown/index.html b/docs/zh-CN/1.1.5/doc-markdown/index.html new file mode 100644 index 0000000000..12250424c1 --- /dev/null +++ b/docs/zh-CN/1.1.5/doc-markdown/index.html @@ -0,0 +1,178 @@ +Markdown Features · Docusaurus

1.1.5

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The url for editing this document. If this field is not present, the document's edit url will fallback to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

博客文章使用以下markdown字段, 它们由两边的行 --- 括起来:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

您可以使用相关urls 链接到其他文档文件, 这样它们将自动转换为相应的 html 链接。

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

这可以帮助您在 GitHub 上浏览文档, 因为这样的链接将会功能链接到其他文档 (但仍在 GitHub), 但文档在得到渲染时将具有正确的 html 链接。

+

链接到图像和其它资源

+

使用相关 url 可以以与文档相同的方式链接静态资源。 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

您可以制作一个自动生成的链接列表, 它可以作为 API 文档的目录使用。

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(
+  <h1>Hello, world!</h1>,
+  document.getElementById('root')
+);
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/installation.html b/docs/zh-CN/1.1.5/installation.html new file mode 100644 index 0000000000..a17b762322 --- /dev/null +++ b/docs/zh-CN/1.1.5/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.5

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/installation/index.html b/docs/zh-CN/1.1.5/installation/index.html new file mode 100644 index 0000000000..a17b762322 --- /dev/null +++ b/docs/zh-CN/1.1.5/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.1.5

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    Node版本必须至少为 6.x, 尽管我们推荐 Node 8.x或更高版本。

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/navigation.html b/docs/zh-CN/1.1.5/navigation.html new file mode 100644 index 0000000000..92bea7655f --- /dev/null +++ b/docs/zh-CN/1.1.5/navigation.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.5

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/navigation/index.html b/docs/zh-CN/1.1.5/navigation/index.html new file mode 100644 index 0000000000..92bea7655f --- /dev/null +++ b/docs/zh-CN/1.1.5/navigation/index.html @@ -0,0 +1,214 @@ +Navigation and Sidebars · Docusaurus

1.1.5

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs folder (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+
+

Docusaurus currently does not support documents in nested folders; only in a flat folder structure. We are looking into adding support for nested folders.

+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/publishing.html b/docs/zh-CN/1.1.5/publishing.html new file mode 100644 index 0000000000..c621b6268d --- /dev/null +++ b/docs/zh-CN/1.1.5/publishing.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.5

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/publishing/index.html b/docs/zh-CN/1.1.5/publishing/index.html new file mode 100644 index 0000000000..c621b6268d --- /dev/null +++ b/docs/zh-CN/1.1.5/publishing/index.html @@ -0,0 +1,220 @@ +Publishing your site · Docusaurus

1.1.5

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build folder and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repo is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit Github's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repo that contains the documentation, by checking Settings | Collaborators & teams in the repo.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repo access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub org/repo.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci folder and create a config.yml under that folder.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repo. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repo connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      -run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci folder inside your website/static folder.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repo, or only master branch commits.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/search.html b/docs/zh-CN/1.1.5/search.html new file mode 100644 index 0000000000..3be0f923f2 --- /dev/null +++ b/docs/zh-CN/1.1.5/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.5

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/search/index.html b/docs/zh-CN/1.1.5/search/index.html new file mode 100644 index 0000000000..3be0f923f2 --- /dev/null +++ b/docs/zh-CN/1.1.5/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.1.5

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/site-config.html b/docs/zh-CN/1.1.5/site-config.html new file mode 100644 index 0000000000..3896889cfe --- /dev/null +++ b/docs/zh-CN/1.1.5/site-config.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.5

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/site-config/index.html b/docs/zh-CN/1.1.5/site-config/index.html new file mode 100644 index 0000000000..3896889cfe --- /dev/null +++ b/docs/zh-CN/1.1.5/site-config/index.html @@ -0,0 +1,247 @@ +siteConfig.js · Docusaurus

1.1.5

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - 网站图标的url。

+

headerIcon - 标题导航栏中使用的图标的 url。

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repo project name (case sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - url for your site.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cname - The CNAME for your website. It will go into a CNAME file when your site it built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field. Note that all of your documentation *.md files must still reside in a flat hierarchy. You cannot have your documents in nested directories.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - url for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family css configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Folders inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the url and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/site-creation.html b/docs/zh-CN/1.1.5/site-creation.html new file mode 100644 index 0000000000..4ed9a2a67b --- /dev/null +++ b/docs/zh-CN/1.1.5/site-creation.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.5

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/site-creation/index.html b/docs/zh-CN/1.1.5/site-creation/index.html new file mode 100644 index 0000000000..4ed9a2a67b --- /dev/null +++ b/docs/zh-CN/1.1.5/site-creation/index.html @@ -0,0 +1,138 @@ +Creating your site · Docusaurus

1.1.5

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-of-repo
+├── docs
+├── website
+│   ├── blog
+│   ├── core
+│   │   └── Footer.js
+│   ├── node_modules
+│   ├── package.json
+│   ├── pages
+│   ├── sidebars.json
+│   ├── siteConfig.js
+│   └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs folder as markdown .md files. Any blog posts should be inside the blog folder.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs folder as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    +
    +

    If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

    +
    3. +

  3. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.

    4. +

  4. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.

    5. +

  5. Place assets, such as images, in the website/static/ folder.

    6. +

  6. Run the site to see the results of your changes.

    +
    cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
    7. +
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static folder with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/site-preparation.html b/docs/zh-CN/1.1.5/site-preparation.html new file mode 100644 index 0000000000..4bb87c507b --- /dev/null +++ b/docs/zh-CN/1.1.5/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.5

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/site-preparation/index.html b/docs/zh-CN/1.1.5/site-preparation/index.html new file mode 100644 index 0000000000..4bb87c507b --- /dev/null +++ b/docs/zh-CN/1.1.5/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.1.5

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • website/blog-examples-from-docusaurus文件夹中包含使用markdown写的博客示范文章。
    • +
  • docs-examples-from-docusaurus文件夹中包含使用markdown写的示范文档文件。
    • +
  • website/pages文件夹中包含示例网站的顶层页面。
    • +
  • website/static 文件夹包含示例网站使用的静态资源。
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

你不能删除 website/pages 和 website/static 文件夹, 但可以按你的意愿改变里面的内容。 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/translation.html b/docs/zh-CN/1.1.5/translation.html new file mode 100644 index 0000000000..31345f8d3c --- /dev/null +++ b/docs/zh-CN/1.1.5/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.5

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/translation/index.html b/docs/zh-CN/1.1.5/translation/index.html new file mode 100644 index 0000000000..31345f8d3c --- /dev/null +++ b/docs/zh-CN/1.1.5/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.1.5

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

需要翻译文本的网页应放在 website/pages/en 文件夹中。

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/*.md'
+    translation: '/website/translated_docs/%locale%/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/versioning.html b/docs/zh-CN/1.1.5/versioning.html new file mode 100644 index 0000000000..afed172b96 --- /dev/null +++ b/docs/zh-CN/1.1.5/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.5

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.1.5/versioning/index.html b/docs/zh-CN/1.1.5/versioning/index.html new file mode 100644 index 0000000000..afed172b96 --- /dev/null +++ b/docs/zh-CN/1.1.5/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.1.5

Translate

Versioning

可以使用 version 脚本，根据 docs 目录中的最新内容生成新的文档版本。 然后, 即使 docs 目录的文档继续更改, 这些特定文档集仍将被保留和访问。

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs folder and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs folder will be considered part of version next and they are available, for example, at the url docs/next/doc1.html. Documents from the latest version use the url docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the url docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs folder and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs folder. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the folder translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/api-pages.html b/docs/zh-CN/1.2.0/api-pages.html new file mode 100644 index 0000000000..09ee08d339 --- /dev/null +++ b/docs/zh-CN/1.2.0/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/api-pages/index.html b/docs/zh-CN/1.2.0/api-pages/index.html new file mode 100644 index 0000000000..09ee08d339 --- /dev/null +++ b/docs/zh-CN/1.2.0/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/blog.html b/docs/zh-CN/1.2.0/blog.html new file mode 100644 index 0000000000..baf68c55ea --- /dev/null +++ b/docs/zh-CN/1.2.0/blog.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.2.0

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/blog/index.html b/docs/zh-CN/1.2.0/blog/index.html new file mode 100644 index 0000000000..baf68c55ea --- /dev/null +++ b/docs/zh-CN/1.2.0/blog/index.html @@ -0,0 +1,182 @@ +Adding a Blog · Docusaurus

1.2.0

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/commands.html b/docs/zh-CN/1.2.0/commands.html new file mode 100644 index 0000000000..068135a263 --- /dev/null +++ b/docs/zh-CN/1.2.0/commands.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.2.0

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/commands/index.html b/docs/zh-CN/1.2.0/commands/index.html new file mode 100644 index 0000000000..068135a263 --- /dev/null +++ b/docs/zh-CN/1.2.0/commands/index.html @@ -0,0 +1,178 @@ +CLI Commands · Docusaurus

1.2.0

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/custom-pages.html b/docs/zh-CN/1.2.0/custom-pages.html new file mode 100644 index 0000000000..c29f15692f --- /dev/null +++ b/docs/zh-CN/1.2.0/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/custom-pages/index.html b/docs/zh-CN/1.2.0/custom-pages/index.html new file mode 100644 index 0000000000..c29f15692f --- /dev/null +++ b/docs/zh-CN/1.2.0/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/doc-markdown.html b/docs/zh-CN/1.2.0/doc-markdown.html new file mode 100644 index 0000000000..08e58a14fd --- /dev/null +++ b/docs/zh-CN/1.2.0/doc-markdown.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.0

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/doc-markdown/index.html b/docs/zh-CN/1.2.0/doc-markdown/index.html new file mode 100644 index 0000000000..08e58a14fd --- /dev/null +++ b/docs/zh-CN/1.2.0/doc-markdown/index.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.0

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/installation.html b/docs/zh-CN/1.2.0/installation.html new file mode 100644 index 0000000000..b4383ada36 --- /dev/null +++ b/docs/zh-CN/1.2.0/installation.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.2.0

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/installation/index.html b/docs/zh-CN/1.2.0/installation/index.html new file mode 100644 index 0000000000..b4383ada36 --- /dev/null +++ b/docs/zh-CN/1.2.0/installation/index.html @@ -0,0 +1,114 @@ +Installation · Docusaurus

1.2.0

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

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 can update to the latest version of Docusaurus by typing yarn upgrade docusaurus --latest or npm update docusaurus.

+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/navigation.html b/docs/zh-CN/1.2.0/navigation.html new file mode 100644 index 0000000000..2da58d24ef --- /dev/null +++ b/docs/zh-CN/1.2.0/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/navigation/index.html b/docs/zh-CN/1.2.0/navigation/index.html new file mode 100644 index 0000000000..2da58d24ef --- /dev/null +++ b/docs/zh-CN/1.2.0/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/publishing.html b/docs/zh-CN/1.2.0/publishing.html new file mode 100644 index 0000000000..7b4fd25c8d --- /dev/null +++ b/docs/zh-CN/1.2.0/publishing.html @@ -0,0 +1,255 @@ +Publishing your site · Docusaurus

1.2.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/publishing/index.html b/docs/zh-CN/1.2.0/publishing/index.html new file mode 100644 index 0000000000..7b4fd25c8d --- /dev/null +++ b/docs/zh-CN/1.2.0/publishing/index.html @@ -0,0 +1,255 @@ +Publishing your site · Docusaurus

1.2.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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.

+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/search.html b/docs/zh-CN/1.2.0/search.html new file mode 100644 index 0000000000..610652218c --- /dev/null +++ b/docs/zh-CN/1.2.0/search.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.2.0

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/search/index.html b/docs/zh-CN/1.2.0/search/index.html new file mode 100644 index 0000000000..610652218c --- /dev/null +++ b/docs/zh-CN/1.2.0/search/index.html @@ -0,0 +1,96 @@ +Enabling Search · Docusaurus

1.2.0

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/site-config.html b/docs/zh-CN/1.2.0/site-config.html new file mode 100644 index 0000000000..d50f2136fa --- /dev/null +++ b/docs/zh-CN/1.2.0/site-config.html @@ -0,0 +1,257 @@ +siteConfig.js · Docusaurus

1.2.0

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/site-config/index.html b/docs/zh-CN/1.2.0/site-config/index.html new file mode 100644 index 0000000000..d50f2136fa --- /dev/null +++ b/docs/zh-CN/1.2.0/site-config/index.html @@ -0,0 +1,257 @@ +siteConfig.js · Docusaurus

1.2.0

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/site-creation.html b/docs/zh-CN/1.2.0/site-creation.html new file mode 100644 index 0000000000..19dba73e21 --- /dev/null +++ b/docs/zh-CN/1.2.0/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/site-creation/index.html b/docs/zh-CN/1.2.0/site-creation/index.html new file mode 100644 index 0000000000..19dba73e21 --- /dev/null +++ b/docs/zh-CN/1.2.0/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/site-preparation.html b/docs/zh-CN/1.2.0/site-preparation.html new file mode 100644 index 0000000000..7d12d8ee91 --- /dev/null +++ b/docs/zh-CN/1.2.0/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.0

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/site-preparation/index.html b/docs/zh-CN/1.2.0/site-preparation/index.html new file mode 100644 index 0000000000..7d12d8ee91 --- /dev/null +++ b/docs/zh-CN/1.2.0/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.0

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/translation.html b/docs/zh-CN/1.2.0/translation.html new file mode 100644 index 0000000000..4268be38dd --- /dev/null +++ b/docs/zh-CN/1.2.0/translation.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.2.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/translation/index.html b/docs/zh-CN/1.2.0/translation/index.html new file mode 100644 index 0000000000..4268be38dd --- /dev/null +++ b/docs/zh-CN/1.2.0/translation/index.html @@ -0,0 +1,239 @@ +Translations & Localization · Docusaurus

1.2.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/versioning.html b/docs/zh-CN/1.2.0/versioning.html new file mode 100644 index 0000000000..81dedb880b --- /dev/null +++ b/docs/zh-CN/1.2.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.0/versioning/index.html b/docs/zh-CN/1.2.0/versioning/index.html new file mode 100644 index 0000000000..81dedb880b --- /dev/null +++ b/docs/zh-CN/1.2.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/api-pages.html b/docs/zh-CN/1.2.1/api-pages.html new file mode 100644 index 0000000000..5cb4af2c0d --- /dev/null +++ b/docs/zh-CN/1.2.1/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/api-pages/index.html b/docs/zh-CN/1.2.1/api-pages/index.html new file mode 100644 index 0000000000..5cb4af2c0d --- /dev/null +++ b/docs/zh-CN/1.2.1/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.2.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/blog.html b/docs/zh-CN/1.2.1/blog.html new file mode 100644 index 0000000000..d7c4aa0fee --- /dev/null +++ b/docs/zh-CN/1.2.1/blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.2.1

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/blog/index.html b/docs/zh-CN/1.2.1/blog/index.html new file mode 100644 index 0000000000..d7c4aa0fee --- /dev/null +++ b/docs/zh-CN/1.2.1/blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.2.1

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/commands.html b/docs/zh-CN/1.2.1/commands.html new file mode 100644 index 0000000000..7ed9ec0dc6 --- /dev/null +++ b/docs/zh-CN/1.2.1/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.2.1

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/commands/index.html b/docs/zh-CN/1.2.1/commands/index.html new file mode 100644 index 0000000000..7ed9ec0dc6 --- /dev/null +++ b/docs/zh-CN/1.2.1/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.2.1

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/custom-pages.html b/docs/zh-CN/1.2.1/custom-pages.html new file mode 100644 index 0000000000..8ffd2aece2 --- /dev/null +++ b/docs/zh-CN/1.2.1/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/custom-pages/index.html b/docs/zh-CN/1.2.1/custom-pages/index.html new file mode 100644 index 0000000000..8ffd2aece2 --- /dev/null +++ b/docs/zh-CN/1.2.1/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.2.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← 上一页Enabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/doc-markdown.html b/docs/zh-CN/1.2.1/doc-markdown.html new file mode 100644 index 0000000000..0734359f39 --- /dev/null +++ b/docs/zh-CN/1.2.1/doc-markdown.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.1

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/doc-markdown/index.html b/docs/zh-CN/1.2.1/doc-markdown/index.html new file mode 100644 index 0000000000..0734359f39 --- /dev/null +++ b/docs/zh-CN/1.2.1/doc-markdown/index.html @@ -0,0 +1,193 @@ +Markdown Features · Docusaurus

1.2.1

Translate

Markdown Features

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
* `docusaurus.function(a, b)`
+* `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/installation.html b/docs/zh-CN/1.2.1/installation.html new file mode 100644 index 0000000000..7178f2a81e --- /dev/null +++ b/docs/zh-CN/1.2.1/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.2.1

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/installation/index.html b/docs/zh-CN/1.2.1/installation/index.html new file mode 100644 index 0000000000..7178f2a81e --- /dev/null +++ b/docs/zh-CN/1.2.1/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.2.1

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/navigation.html b/docs/zh-CN/1.2.1/navigation.html new file mode 100644 index 0000000000..887cda6080 --- /dev/null +++ b/docs/zh-CN/1.2.1/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/navigation/index.html b/docs/zh-CN/1.2.1/navigation/index.html new file mode 100644 index 0000000000..887cda6080 --- /dev/null +++ b/docs/zh-CN/1.2.1/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.2.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/publishing.html b/docs/zh-CN/1.2.1/publishing.html new file mode 100644 index 0000000000..8939abe656 --- /dev/null +++ b/docs/zh-CN/1.2.1/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.2.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/publishing/index.html b/docs/zh-CN/1.2.1/publishing/index.html new file mode 100644 index 0000000000..8939abe656 --- /dev/null +++ b/docs/zh-CN/1.2.1/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.2.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your site下一页 →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/search.html b/docs/zh-CN/1.2.1/search.html new file mode 100644 index 0000000000..67aa33e395 --- /dev/null +++ b/docs/zh-CN/1.2.1/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.2.1

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/search/index.html b/docs/zh-CN/1.2.1/search/index.html new file mode 100644 index 0000000000..67aa33e395 --- /dev/null +++ b/docs/zh-CN/1.2.1/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.2.1

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/site-config.html b/docs/zh-CN/1.2.1/site-config.html new file mode 100644 index 0000000000..e10a5f0a0f --- /dev/null +++ b/docs/zh-CN/1.2.1/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.2.1

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/site-config/index.html b/docs/zh-CN/1.2.1/site-config/index.html new file mode 100644 index 0000000000..e10a5f0a0f --- /dev/null +++ b/docs/zh-CN/1.2.1/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.2.1

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/site-creation.html b/docs/zh-CN/1.2.1/site-creation.html new file mode 100644 index 0000000000..d2ef0a26db --- /dev/null +++ b/docs/zh-CN/1.2.1/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/site-creation/index.html b/docs/zh-CN/1.2.1/site-creation/index.html new file mode 100644 index 0000000000..d2ef0a26db --- /dev/null +++ b/docs/zh-CN/1.2.1/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.2.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/site-preparation.html b/docs/zh-CN/1.2.1/site-preparation.html new file mode 100644 index 0000000000..80e7e7101b --- /dev/null +++ b/docs/zh-CN/1.2.1/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.1

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/site-preparation/index.html b/docs/zh-CN/1.2.1/site-preparation/index.html new file mode 100644 index 0000000000..80e7e7101b --- /dev/null +++ b/docs/zh-CN/1.2.1/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.2.1

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/translation.html b/docs/zh-CN/1.2.1/translation.html new file mode 100644 index 0000000000..12f75bbab4 --- /dev/null +++ b/docs/zh-CN/1.2.1/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.2.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/translation/index.html b/docs/zh-CN/1.2.1/translation/index.html new file mode 100644 index 0000000000..12f75bbab4 --- /dev/null +++ b/docs/zh-CN/1.2.1/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.2.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/versioning.html b/docs/zh-CN/1.2.1/versioning.html new file mode 100644 index 0000000000..5017a7fdae --- /dev/null +++ b/docs/zh-CN/1.2.1/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.2.1/versioning/index.html b/docs/zh-CN/1.2.1/versioning/index.html new file mode 100644 index 0000000000..5017a7fdae --- /dev/null +++ b/docs/zh-CN/1.2.1/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.2.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/adding-blog.html b/docs/zh-CN/1.3.0/adding-blog.html new file mode 100644 index 0000000000..a9d986ff9b --- /dev/null +++ b/docs/zh-CN/1.3.0/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/adding-blog/index.html b/docs/zh-CN/1.3.0/adding-blog/index.html new file mode 100644 index 0000000000..a9d986ff9b --- /dev/null +++ b/docs/zh-CN/1.3.0/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/api-pages.html b/docs/zh-CN/1.3.0/api-pages.html new file mode 100644 index 0000000000..bf86558ca6 --- /dev/null +++ b/docs/zh-CN/1.3.0/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/api-pages/index.html b/docs/zh-CN/1.3.0/api-pages/index.html new file mode 100644 index 0000000000..bf86558ca6 --- /dev/null +++ b/docs/zh-CN/1.3.0/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.0

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/blog.html b/docs/zh-CN/1.3.0/blog.html new file mode 100644 index 0000000000..1a366ed37e --- /dev/null +++ b/docs/zh-CN/1.3.0/blog.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/blog/index.html b/docs/zh-CN/1.3.0/blog/index.html new file mode 100644 index 0000000000..1a366ed37e --- /dev/null +++ b/docs/zh-CN/1.3.0/blog/index.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.0

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/commands.html b/docs/zh-CN/1.3.0/commands.html new file mode 100644 index 0000000000..6a1c61ac86 --- /dev/null +++ b/docs/zh-CN/1.3.0/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.0

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/commands/index.html b/docs/zh-CN/1.3.0/commands/index.html new file mode 100644 index 0000000000..6a1c61ac86 --- /dev/null +++ b/docs/zh-CN/1.3.0/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.0

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/custom-pages.html b/docs/zh-CN/1.3.0/custom-pages.html new file mode 100644 index 0000000000..5d30d89978 --- /dev/null +++ b/docs/zh-CN/1.3.0/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/custom-pages/index.html b/docs/zh-CN/1.3.0/custom-pages/index.html new file mode 100644 index 0000000000..5d30d89978 --- /dev/null +++ b/docs/zh-CN/1.3.0/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.0

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/doc-markdown.html b/docs/zh-CN/1.3.0/doc-markdown.html new file mode 100644 index 0000000000..f5f6866552 --- /dev/null +++ b/docs/zh-CN/1.3.0/doc-markdown.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.0

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/doc-markdown/index.html b/docs/zh-CN/1.3.0/doc-markdown/index.html new file mode 100644 index 0000000000..f5f6866552 --- /dev/null +++ b/docs/zh-CN/1.3.0/doc-markdown/index.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.0

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/installation.html b/docs/zh-CN/1.3.0/installation.html new file mode 100644 index 0000000000..41ca92aa85 --- /dev/null +++ b/docs/zh-CN/1.3.0/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.0

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/installation/index.html b/docs/zh-CN/1.3.0/installation/index.html new file mode 100644 index 0000000000..41ca92aa85 --- /dev/null +++ b/docs/zh-CN/1.3.0/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.0

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/navigation.html b/docs/zh-CN/1.3.0/navigation.html new file mode 100644 index 0000000000..8ee5c984ee --- /dev/null +++ b/docs/zh-CN/1.3.0/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/navigation/index.html b/docs/zh-CN/1.3.0/navigation/index.html new file mode 100644 index 0000000000..8ee5c984ee --- /dev/null +++ b/docs/zh-CN/1.3.0/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.0

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/publishing.html b/docs/zh-CN/1.3.0/publishing.html new file mode 100644 index 0000000000..21fa83b593 --- /dev/null +++ b/docs/zh-CN/1.3.0/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/publishing/index.html b/docs/zh-CN/1.3.0/publishing/index.html new file mode 100644 index 0000000000..21fa83b593 --- /dev/null +++ b/docs/zh-CN/1.3.0/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.0

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/search.html b/docs/zh-CN/1.3.0/search.html new file mode 100644 index 0000000000..7e5334ce43 --- /dev/null +++ b/docs/zh-CN/1.3.0/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.0

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/search/index.html b/docs/zh-CN/1.3.0/search/index.html new file mode 100644 index 0000000000..7e5334ce43 --- /dev/null +++ b/docs/zh-CN/1.3.0/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.0

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/site-config.html b/docs/zh-CN/1.3.0/site-config.html new file mode 100644 index 0000000000..41913e2f37 --- /dev/null +++ b/docs/zh-CN/1.3.0/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.0

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/site-config/index.html b/docs/zh-CN/1.3.0/site-config/index.html new file mode 100644 index 0000000000..41913e2f37 --- /dev/null +++ b/docs/zh-CN/1.3.0/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.0

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/site-creation.html b/docs/zh-CN/1.3.0/site-creation.html new file mode 100644 index 0000000000..90ad23b118 --- /dev/null +++ b/docs/zh-CN/1.3.0/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/site-creation/index.html b/docs/zh-CN/1.3.0/site-creation/index.html new file mode 100644 index 0000000000..90ad23b118 --- /dev/null +++ b/docs/zh-CN/1.3.0/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.0

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/site-preparation.html b/docs/zh-CN/1.3.0/site-preparation.html new file mode 100644 index 0000000000..4bfd59e23f --- /dev/null +++ b/docs/zh-CN/1.3.0/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.0

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/site-preparation/index.html b/docs/zh-CN/1.3.0/site-preparation/index.html new file mode 100644 index 0000000000..4bfd59e23f --- /dev/null +++ b/docs/zh-CN/1.3.0/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.0

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/translation.html b/docs/zh-CN/1.3.0/translation.html new file mode 100644 index 0000000000..fe624d0133 --- /dev/null +++ b/docs/zh-CN/1.3.0/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/translation/index.html b/docs/zh-CN/1.3.0/translation/index.html new file mode 100644 index 0000000000..fe624d0133 --- /dev/null +++ b/docs/zh-CN/1.3.0/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.0

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/versioning.html b/docs/zh-CN/1.3.0/versioning.html new file mode 100644 index 0000000000..04df5f3cff --- /dev/null +++ b/docs/zh-CN/1.3.0/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/1.3.0/versioning/index.html b/docs/zh-CN/1.3.0/versioning/index.html new file mode 100644 index 0000000000..04df5f3cff --- /dev/null +++ b/docs/zh-CN/1.3.0/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.0

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/adding-blog.html b/docs/zh-CN/adding-blog.html new file mode 100644 index 0000000000..854edd4f2d --- /dev/null +++ b/docs/zh-CN/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/adding-blog/index.html b/docs/zh-CN/adding-blog/index.html new file mode 100644 index 0000000000..854edd4f2d --- /dev/null +++ b/docs/zh-CN/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/api-pages.html b/docs/zh-CN/api-pages.html new file mode 100644 index 0000000000..042447c3ca --- /dev/null +++ b/docs/zh-CN/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/api-pages/index.html b/docs/zh-CN/api-pages/index.html new file mode 100644 index 0000000000..042447c3ca --- /dev/null +++ b/docs/zh-CN/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

1.3.1

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/blog.html b/docs/zh-CN/blog.html new file mode 100644 index 0000000000..c7d1053ced --- /dev/null +++ b/docs/zh-CN/blog.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/zh-CN/blog/index.html b/docs/zh-CN/blog/index.html new file mode 100644 index 0000000000..c7d1053ced --- /dev/null +++ b/docs/zh-CN/blog/index.html @@ -0,0 +1,165 @@ +Adding a Blog · Docusaurus

1.3.1

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
\ No newline at end of file diff --git a/docs/zh-CN/commands.html b/docs/zh-CN/commands.html new file mode 100644 index 0000000000..9b539b85c8 --- /dev/null +++ b/docs/zh-CN/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.1

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/commands/index.html b/docs/zh-CN/commands/index.html new file mode 100644 index 0000000000..9b539b85c8 --- /dev/null +++ b/docs/zh-CN/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

1.3.1

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/custom-pages.html b/docs/zh-CN/custom-pages.html new file mode 100644 index 0000000000..c0acfc4f27 --- /dev/null +++ b/docs/zh-CN/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/custom-pages/index.html b/docs/zh-CN/custom-pages/index.html new file mode 100644 index 0000000000..c0acfc4f27 --- /dev/null +++ b/docs/zh-CN/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

1.3.1

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/doc-markdown.html b/docs/zh-CN/doc-markdown.html new file mode 100644 index 0000000000..bb425a5f7d --- /dev/null +++ b/docs/zh-CN/doc-markdown.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.1

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/doc-markdown/index.html b/docs/zh-CN/doc-markdown/index.html new file mode 100644 index 0000000000..bb425a5f7d --- /dev/null +++ b/docs/zh-CN/doc-markdown/index.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

1.3.1

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/installation.html b/docs/zh-CN/installation.html new file mode 100644 index 0000000000..45c754a531 --- /dev/null +++ b/docs/zh-CN/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.1

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/installation/index.html b/docs/zh-CN/installation/index.html new file mode 100644 index 0000000000..45c754a531 --- /dev/null +++ b/docs/zh-CN/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

1.3.1

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/navigation.html b/docs/zh-CN/navigation.html new file mode 100644 index 0000000000..4542a9bfe7 --- /dev/null +++ b/docs/zh-CN/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/navigation/index.html b/docs/zh-CN/navigation/index.html new file mode 100644 index 0000000000..4542a9bfe7 --- /dev/null +++ b/docs/zh-CN/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

1.3.1

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/next/adding-blog.html b/docs/zh-CN/next/adding-blog.html new file mode 100644 index 0000000000..ab356e95a6 --- /dev/null +++ b/docs/zh-CN/next/adding-blog.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

next

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/next/adding-blog/index.html b/docs/zh-CN/next/adding-blog/index.html new file mode 100644 index 0000000000..ab356e95a6 --- /dev/null +++ b/docs/zh-CN/next/adding-blog/index.html @@ -0,0 +1,188 @@ +Adding a Blog · Docusaurus

next

Translate

Adding a Blog

初始设置

+

To setup your site's blog, start by creating a blog directory within your repo's website directory.

+

然后, 在 siteConfig.js 中添加一个指向您博客的 headerLinks:

+
headerLinks: [
+    ...
+    { blog: true, label: 'Blog' },
+    ...
+]
+
+

添加文章

+

To publish in the blog, create a file within the blog directory with a formatted name of YYYY-MM-DD-My-Blog-Post-Title.md. The post date is extracted from the file name.

+

例如, 文件 website/blog/2017-08-18-Introducing-Docusaurus.md:

+
---
+author: Frank Li
+authorURL: https://twitter.com/foobarbaz
+authorFBID: 503283835
+title: Introducing Docusaurus
+---
+
+Lorem Ipsum...
+
+

顶部选项

+

唯一必填项是 title；但是, 我们还提供了添加可选的文章作者信息的功能。

+
    +
  • author - 作者署名的文本标签。
    • +
  • authorURL - The URL associated with the author. This could be a Twitter, GitHub, Facebook account, etc.
    • +
  • authorFBID - The Facebook profile ID that is used to fetch the profile picture.
    • +
  • authorImageURL - The URL to the author's image. (Note: If you use both authorFBID and authorImageURL, authorFBID will take precedence. Don't include authorFBID if you want authorImageURL to appear.)
    • +
  • title - The blog post title.
    • +
+

摘要截取

+

Use the <!--truncate--> marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. <!--truncate--> 标记以上的内容都会成为摘要。 例如：

+
---
+title: Truncation Example
+---
+
+All this will be part of the blog post summary.
+
+Even this.
+
+<!--truncate-->
+
+But anything from here on down will not be.
+
+Not this.
+
+Or this.
+
+

修改侧边栏可见的文章数

+

默认情况下，侧边栏会显示最近的5篇文章。

+

你可以在 siteConfig.js中添加 blogSidebarCount属性，来配置你的想要展示的文章数。

+

The available options are an integer representing the number of posts you wish to show or a string with the value 'ALL'.

+

例如：

+
blogSidebarCount: 'ALL';
+
+

Changing The Sidebar Title

+

You can configure a specific sidebar title by adding a blogSidebarTitle setting to your siteConfig.js.

+

The option is an object which can have the keys default and all. Specifying a value for default allows you to change the default sidebar title. Specifying a value for all allows you to change the sidebar title when the blogSidebarCount option is set to 'ALL'.

+

例如：

+
blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
+
+

RSS订阅

+

Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically to your website page's HTML

+

+标签

+

+ A summary of the post's text is provided in the RSS feed up to the <!--truncate-->. If no <!--truncate--> tag is found, then all text up 250 characters are used. +

+

+社交按钮 +

+

+ 如果想在文章底部显示Facebook与(或)Twitter社交按钮，那么在网站设置的siteConfig.js中配置facebookAppId 与(或) twitter选项。 +

+

+Advanced Topics +

+

+I want to run in "Blog Only" mode. +

+

+ You can run your Docusaurus site without a landing page and instead have your blog load first. +

+

+ To do this: +

+
    +
  1. + Create a file index.html in website/static/. +
    2. +
    <li>
+  Place the contents of the template below into <code>website/static/index.html</code>
+</li>
+
+<li>
+  Customize the <code>&lt;title&gt;</code> of <code>website/static/index.html</code>
+</li>
+
+<li>
+  Delete the dynamic landing page <code>website/pages/en/index.js</code>
+</li>
+
    +
+
+

+ Now, when Docusaurus generates or builds your site, it will copy the file from static/index.html and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to /blog. +

+
+

+ You can use this template: +

+ 
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=blog/">
+    <script type="text/javascript">
+      window.location.href = 'blog/';
+    </script>
+    <title>Title of Your Blog</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="blog/">link</a>.
+  </body>
+</html>
+
← Publishing your siteCustom Pages →
\ No newline at end of file diff --git a/docs/zh-CN/next/api-pages.html b/docs/zh-CN/next/api-pages.html new file mode 100644 index 0000000000..9e2616625b --- /dev/null +++ b/docs/zh-CN/next/api-pages.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

next

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/next/api-pages/index.html b/docs/zh-CN/next/api-pages/index.html new file mode 100644 index 0000000000..9e2616625b --- /dev/null +++ b/docs/zh-CN/next/api-pages/index.html @@ -0,0 +1,215 @@ +Pages and Styles · Docusaurus

next

Translate

Pages and Styles

Docusaurus provides support for writing pages as React components inside the website/pages directory which will share the same header, footer, and styles as the rest of the site.

+

URLs for Pages

+

Any .js files in website/pages will be rendered to static HTML using the path of the file after pages. website/pages/en中的文件也将会被复制到pages中并且会覆盖pages中的任何同名文件。 For example, the page for the website/pages/en/help.js file will be found at the URL ${baseUrl}en/help.js as well as the URL ${baseUrl}help.js, where ${baseUrl} is the baseUrl field set in your siteConfig.js file.

+

Titles for Pages

+

By default, the title of your page is <title> • <tagline> where title and tagline fields are set in siteConfig.js. You can exclude the tagline in the title by setting disableTitleTagline to true. If you want to set a specific title for your custom pages, add a title class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.title = 'My Custom Title';
+
+module.exports = MyPage;
+
+

Description for Pages

+

By default, the description your page is tagline set in siteConfig.js. If you want to set a specific description for your custom pages, add a description class property on your exported React component.

+

例如：

+
const React = require('react');
+
+class MyPage extends React.Component {
+  render() {
+    // ... your rendering code
+  }
+}
+
+MyPage.description = 'My Custom Description';
+
+module.exports = MyPage;
+
+

This will be translated to a description metadata tag on the generated HTML.

+
<meta property="og:description" content="My Custom Description"/>
+<meta name="description" content="My Custom Description"/>
+
+

Page Require Paths

+

Docusaurus provides a few useful React components for users to write their own pages, found in the CompLibrary module. This module is provided as part of Docusaurus in node_modules/docusaurus, so to access it, pages in the pages directory are temporarily copied into node_modules/docusaurus when rendering to static HTML. As seen in the example files, this means that a user page at pages/en/index.js uses a require path to '../../core/CompLibrary.js' to import the provided components.

+

What this means to the user is that if you wish to use the CompLibrary module, make sure the require path is set correctly. For example, a page at page/mypage.js would use a path '../core/CompLibrary.js'.

+

If you wish to use your own components inside the website directory, use process.cwd() which will refer to the website directory to construct require paths. For example, if you add a component to website/core/mycomponent.js, you can use the require path, 'process.cwd() + /core/mycomponent.js'.

+

Provided Components

+

Docusaurus provides the following components in CompLibrary:

+

CompLibrary.MarkdownBlock

+

A React component that parses markdown and renders to HTML.

+

例如：

+
const MarkdownBlock = CompLibrary.MarkdownBlock;
+
+<MarkdownBlock>
+  [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
+
+

CompLibrary.Container

+

A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.

+

Props

+ + + + + + + + + +
PropTypeDefaultDescription
paddingArray of 'all', 'bottom', 'left', 'right', 'top'[]Positions of the padding.
backgroundOne of 'dark', 'highlight', 'light'nullBackground styling of the element.
classNameString-Custom class to add to the element.
+

Example

+
<Container
+  padding={['bottom', 'top']}
+  background="light"
+  className="myCustomClass">
+  ...
+</Container>
+
+

CompLibrary.GridBlock

+

A React component to organize text and images.

+

Props

+ + + + + + + + + + +
PropTypeDefaultDescription
alignOne of 'left', 'center', 'right''left'Text alignment of content.
layoutOne of 'twoColumn', 'threeColumn', 'fourColumn''twoColumn'Number of column sections in the GridBlock.
classNameString-Custom class to add to the element.
contentsArray of content objects[]Contents of each section of the GridBlock. Refer to the next table for the fields available on a content object.
+

Content Object

+ + + + + + + + + + + + +
KeyTypeDefaultDescription
titleString-The display title of this section, which is parsed using Markdown
contentString-The text of this section, which is parsed using Markdown
imageString-The path of the display image
imageAltString-The text that will be shown in case the image is not available
imageAlignOne of 'top', 'left', 'bottom', 'right''left'Image alignment relative to the text
imageLinkString-Link destination from clicking the image
+

Example

+
<GridBlock
+  align="center"
+  layout="threeColumn"
+  className="myCustomClass"
+  contents={[
+    {
+      title: `[Learn](${siteConfig.baseUrl}docs/tutorial.html)`,
+      content: 'Learn how to use this project',
+      image: siteConfig.baseUrl + 'img/learn.png',
+      imageAlt: 'Learn how to use this project',
+      imageLink: siteConfig.baseUrl + 'docs/tutorial.html',
+    },
+    {
+      title: 'Frequently Asked Questions',
+      content: 'Questions gathered from the community',
+      image: siteConfig.baseUrl + 'img/faq.png',
+      imageAlign: 'top',
+    },
+    {
+      title: 'More',
+      content: 'Lots of documentation is on this site',
+    },
+  ]}
+/>
+
+

More examples of how these components are used can be found in the generated example files as well as in Docusaurus' own repository for its website set-up.

+

Translating Strings

+

When translations are enabled, any pages inside website/pages/en will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js file. E.g. The URL for a French page of website/pages/en/help.js would be found at ${baseUrl}fr/help.html.

+

When writing pages that you wish to translate, wrap any strings to be translated inside a <translate> tag. e.g.,

+
<p>
+  <translate>I like translations</translate>
+</p>
+
+

You can also provide an optional description attribute to provide context for translators. e.g,

+
<a href="/community">
+  <translate desc="Footer link to page referring to community GitHub and Slack">
+    Community
+  </translate>
+</a>
+
+

Add the following require statement as well:

+
const translate = require('../../server/translate.js').translate;
+
+

Note that this path is valid for files inside pages/en and should be adjusted accordingly if files are in different locations, as discussed above.

+

Using Static Assets

+

Static assets should be placed into the website/static directory. They can be accessed by their paths, excluding static. For example, if the site's baseUrl is /docusaurus/, an image in website/static/img/logo.png is available at /docusaurus/img/logo.png.

+

Styles

+

You should configure your site's primary, secondary, and code block colors using the colors field in siteConfig as specified here. You can also configure other colors in the same way as described in the siteConfig doc.

+

You can provide your own custom styles by adding them anywhere in the website/static directory. Any .css files you provide in the static directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.

+

An easy way to figure out what classes you wish to override or add to is to start your server locally and use your browser's inspect element tool.

+
← Markdown FeaturessiteConfig.js →
\ No newline at end of file diff --git a/docs/zh-CN/next/commands.html b/docs/zh-CN/next/commands.html new file mode 100644 index 0000000000..5cdfa2a4ca --- /dev/null +++ b/docs/zh-CN/next/commands.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

next

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/next/commands/index.html b/docs/zh-CN/next/commands/index.html new file mode 100644 index 0000000000..5cdfa2a4ca --- /dev/null +++ b/docs/zh-CN/next/commands/index.html @@ -0,0 +1,179 @@ +CLI Commands · Docusaurus

next

Translate

CLI Commands

Docusaurus 提供了一组脚本来帮助您生成、服务和配置您的网站。 使用 Yarn 或 npm 时, 可以使用 run 命令调用这些脚本。 一些常见的命令如下:

+ +

从命令行运行

+

这些脚本可以使用 Yarn 或 npm 来运行。 如果您已经完成了我们的入门指南, 您可能已经熟悉了 start 命令。 这是这样的命令,：它告诉 Docusaurus 运行 Docusaurus-start 脚本, 它生成站点并启动服务器, 通常是这样调用的:

+
yarn run start
+
+

也可以使用 npm 调用相同的脚本:

+
npm run start
+
+

若要运行特定的脚本, 只需用与脚本关联的命令替换上面示例中的 start 命令。

+

使用参数

+

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
+
+

如果使用 npm 运行 Docusaurus, 则仍然可以通过在 npm run <command> 和命令参数之间插入 -- 来使用命令行参数:

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

配置

+

这些脚本是在 website/package.json 文件的 "scripts" 项下设置的, 作为安装过程的一部分。 如果需要帮助再次设置它们, 请参阅 安装指南 。

+

Docusaurus 提供了一些默认的映像, 允许您按照节点约定运行命令。 您可以键入 yarn run start 或 npm start 来实现相同的目的, 而不是每次都键入 docusaurus-start。

+

命令

+

<autogenerated_table_of_contents>

+
+

参考

+

docusaurus-build

+

别名︰ build。

+ + + + + + + +
OptionsDefaultDescription
--skip-image-compressionfalseSkip compression of image assets. You usually won't want to skip this unless your images have already been optimized.
+

Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.

+

See also docusaurus-start.

+
+

docusaurus-examples

+

别名：examples

+ + + + + + + +
ArgumentsDefaultDescription
<feature>-Specify a feature translations or versions to generate the extra example files for that feature.
+

Example

+
docusaurus-examples <feature>
+
+

When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide.

+
+

docusaurus-发布

+

Alias: publish-gh-pages

+

Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:

+

The following environment variables are generally set manually by the user in the CircleCI config.yml file.

+
    +
  • GIT_USER: 与部署提交联系的 GIT 用户。
    • +
  • USE_SSH: Whether to use SSH instead of HTTPS for your connection to the GitHub repo.
    • +
+

Example

+
GIT_USER=docusaurus-bot USE_SSH=true yarn run publish-gh-pages
+
+

The following environment variables are set by CircleCI during the build process.

+
    +
  • CIRCLE_BRANCH: 与触发 CI 运行的提交关联的 git 分支。
    • +
  • CI_PULL_REQUEST: 如果当前 CI 运行是通过请求中的提交触发的, 则认定为真。
    • +
+

The following should be set by you in siteConfig.js as organizationName and projectName, respectively. If they are not set in your site configuration, they fall back to the CircleCI environment.

+
    +
  • CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the Git repo, e.g. "facebook".
    • +
  • CIRCLE_PROJECT_REPONAME: The name of the Git repo, e.g. "Docusaurus".
    • +
+

You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.

+
+

docusaurus-rename-version

+

Alias: rename-version

+

Renames an existing version of the docs to a new version name.

+ + + + + + + + +
ArgumentsDefaultDescription
<currentVersion>-Version to be renamed.
<newVersion>-Version to be renamed to.
+

Example

+
docusaurus-rename-version <currentVersion> <newVersion>
+
+

See the Versioning guide to learn more.

+
+

docusaurus-start

+

Alias: start.

+

This script will build the static website, apply translations if necessary, and then start a local server.

+ + + + + + + + +
OptionsDefaultDescription
--port <number>3000The website will be served from port 3000 by default, but if the port is taken up, Docusaurus will attempt to find an available one.
--watch-Whether to watch the files and live reload the page when files are changed. Defaults to true. Disable this by using --no-watch.
+
+

docusaurus-版本 <版本>

+

Alias: version

+

Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned directory. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.

+

See the Versioning guide to learn more.

+
+

docusaurus-书写-翻译

+

Alias: write-translations

+

Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.

+
← VersioningMarkdown Features →
\ No newline at end of file diff --git a/docs/zh-CN/next/custom-pages.html b/docs/zh-CN/next/custom-pages.html new file mode 100644 index 0000000000..e280520e5b --- /dev/null +++ b/docs/zh-CN/next/custom-pages.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

next

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/next/custom-pages/index.html b/docs/zh-CN/next/custom-pages/index.html new file mode 100644 index 0000000000..e280520e5b --- /dev/null +++ b/docs/zh-CN/next/custom-pages/index.html @@ -0,0 +1,110 @@ +Custom Pages · Docusaurus

next

Translate

Custom Pages

You can add pages to your site that are not part of the standard docs or blog markdown files. You can do this by adding .js files to the website/pages directory. These files are React components and the render() is called to create them, backed by CSS classes, etc.

+

自定义您的主页

+

The easiest way to get started customizing your home page is to use the example site that was created when you ran the Docusaurus initialization script.

+

You can start your local server and go to http://localhost:3000 to see what the example home page looks like. 在那里，编辑website/pages/en/index.js文件以及它的各种组件来使用你的这个项目需要用到的图像和文本。

+

加入其它自定义页面

+

Docusaurus provides some simple example pages in the website/pages/en directory, including index.js, users.js, and help.js. These are good examples to showcase how to create a custom page for Docusaurus.

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    │   ├── index.js
+    │   ├── users.js
+    │   └── help.js
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. 有关如何使用提供的组件或包含您自己的部件的详细信息, 可在 的 处找到。 有关如何链接到页眉导航栏中的不同页面的信息, 请 的 处找到。

+
+

If you want your page to show up in your navigation header, you will need to update siteConfig.js to add to the headerLinks element. e.g., { page: 'about-slash', label: 'About/' },

+
+

添加静态页面

+

Static .html files can also be used, but they will not include Docusaurus' header, footer, or styles by default. These can be added to the static directory in the same way as other static assets. Alternatively, they can be placed in the pages directory and would be served as-is instead of being rendered from React.

+

If you wish to use Docusaurus' stylesheet, you can access it at ${baseUrl}css/main.css. If you wish to use separate css for these static pages, you can exclude them from being concatenated to Docusaurus' styles by adding them into the siteConfig.separateCss field in siteConfig.js.

+
+

You can set the $wrapPagesHTML site config option in order to wrap raw HTML fragments with the Docusaurus site styling, header and footer.

+
+

自定义您的页脚

+

Starting from the example core/Footer.js file that was created when you ran the Docusaurus initialization script, edit the footer to include any links to pages on your site or other sites that you wish to have.

+

提供的例子有三部分, 左侧有页脚图像, 底部有Facebook 的开源标志和版权。 如果您的项目不是 Facebook 开源项目, 请删除标志和版权。 如果它是facebook的开源项目, 你就可以随意的使用你的页脚, 把它设计成任何你喜欢的样子！

+

一些建议你可能需要提供的链接: 文档, API （应用程序编程接口）, 推特, Discord（一种聊天软件）, facebook群组, Stack Overflow（一个IT技术问答网站）, GitHub（一个开源项目托管平台） 等。

+

Your footer will automatically get applied to all pages on your site, including docs and blog posts. The sole exception to this is any static HTML pages you include.

+

If you do not want a footer for your site, change the render function of core/Footer.js to return null. e.g.,

+
const React = require('react');
+
+class Footer extends React.Component {
+  render() {
+    return null;
+  }
+}
+
+module.exports = Footer;
+
+
← Adding a BlogEnabling Search →
\ No newline at end of file diff --git a/docs/zh-CN/next/doc-markdown.html b/docs/zh-CN/next/doc-markdown.html new file mode 100644 index 0000000000..addf31282d --- /dev/null +++ b/docs/zh-CN/next/doc-markdown.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

next

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/next/doc-markdown/index.html b/docs/zh-CN/next/doc-markdown/index.html new file mode 100644 index 0000000000..addf31282d --- /dev/null +++ b/docs/zh-CN/next/doc-markdown/index.html @@ -0,0 +1,194 @@ +Markdown Features · Docusaurus

next

Translate

Markdown Features

Find out more about Docusaurus-specific fields when writing Markdown.

+

Markdown 标题

+

文档

+

文档使用以下 markdown 协议头字段, 它们由两侧的行 --- 括起来:

+

id: A unique document id. If this field is not present, the document's id will default to its file name (without the extension).

+

title: The title of your document. If this field is not present, the document's title will default to its id.

+

hide_title: Whether to hide the title at the top of the doc.

+

sidebar_label: The text shown in the document sidebar for this document. If this field is not present, the document's sidebar_label will default to its title.

+

例如：

+
---
+id: doc1
+title: My Document
+sidebar_label: Document
+---
+
+

经过版本控制的文档在被复制时会更改其 id 这样才能包含版本号。 新的 id 为 version-${version}-${id}, 其中 ${version} 是该文档的版本号, $ {id} 是原始的 id。 此外，版本文档可得到original_id 文件，使用原版的文件id。

+

例如：

+
---
+id: version-1.0.0-doc1
+title: My Document
+sidebar_label: Document
+original_id: doc1
+---
+
+

custom_edit_url: The URL for editing this document. If this field is not present, the document's edit URL will fall back to editUrl from optional fields of siteConfig.js. See siteConfig.js docs for more information.

+

例如：

+
---
+id: doc-markdown
+title: Markdown Features
+custom_edit_url: https://github.com/facebook/Docusaurus/edit/master/docs/api-doc-markdown.md
+---
+
+

博客文章

+

Blog posts use the following markdown header fields that are enclosed by a line --- on either side:

+

tittle: 此博客文章的标题。

+

author: The author of this blog post. If this field is omitted, no author name will be shown.

+

authorURL: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.

+

authorFBID: 作者的 Facebook（脸书） id, 仅用于让作者的个人资料图片显示在博客文章中。 如果省略此字段, 则不会显示该作者的图片在这篇文章中。

+

例如：

+
---
+tittle: My First Blog Post
+author: Frank Li
+authorURL: http://twitter.com/franchementli
+authorFBID: 100002976521003
+---
+
+

更多功能

+

Docusaurus 在markdown中编写文档时支持一些额外的功能。

+

链接到其他文档

+

You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.

+

例如：

+
[This links to another document](other-document.md)
+
+

这样, markdown将把它自动转换成指向 /docs/other-document.html 的链接(或适当翻译/版本控制链接) 。

+

This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.

+

链接到图像和其它资源

+

Static assets can be linked to in the same way that documents are, using relative URLs. 在文档和博客中使用的静态资产应分别进入 docs/assets 和 website/blog/assets。 Markdown 被转换成正确的链接路径, 这样这些路径就能为所有语言和版本的文档所用。

+

例如：

+
![alt-text](/docs/assets/doc-image.png)
+
+

生成目录

+

You can make an auto-generated list of links, which can be useful as a table of contents for API docs.

+

In your markdown file, insert a line with the text <AUTOGENERATED_TABLE_OF_CONTENTS>. 使用 h3 为标题在代码块里为每个函数编写文档。 These will be found by Docusaurus and a list of links to these sections will inserted at the text <AUTOGENERATED_TABLE_OF_CONTENTS>.

+

例如：

+
### `docusaurus.function(a, b)`
+
+Text describing my function
+
+### `docdoc(file)`
+
+Text describing my function
+
+

这将会把页面带去这些功能的目录：

+
- `docusaurus.function(a, b)`
+- `docdoc(file)`
+
+

每个函数将会把链接带到页面相对应的部分。

+

Syntax Highlighting

+

Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an info string, following the three opening backticks. The following JavaScript example...

+
```js
+ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+```
+
+

...would be rendered with syntax highlighting like so:

+
ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('root'));
+
+

Highlighting is provided by Highlight.js using the theme specified in your siteConfig.js file as part of the highlight key:

+
{
+  ...
+  highlight: {
+    theme: 'default'
+  }
+  ...
+}
+
+

You can find the full list of supported themes in the Highlight.js styles directory.

+

Registering additional languages

+

While Highlight.js provides support for many popular languages out of the box, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the hljs constant as part of the highlight config key. This in turn allows you to call registerLanguage:

+
{
+  ...
+  highlight: {
+    theme: 'default',
+    hljs: function(hljs) {
+      hljs.registerLanguage('galacticbasic', function(hljs) {
+        // ...
+      });
+    }
+  }
+}
+
+

Using Prism as additional syntax highlighter

+

You can also opt to use Prism to syntax highlight certain languages available in the list here. Include those languages in usePrism field in your siteConfig.js

+

例如：

+
// siteConfig.js
+usePrism: ['jsx']
+
+

Notice that the code block below uses JSX syntax highlighting from Prism.

+
class Example extends React.Component {
+  render() {
+    return (
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+        <Text>Docusaurus</Text>
+        <Button
+          title="Click me"
+          onPress={() => this.props.navigation.push('Docusaurus')}
+        />
+      </View>
+    );
+  }
+}
+
+
← CLI CommandsPages and Styles →
\ No newline at end of file diff --git a/docs/zh-CN/next/installation.html b/docs/zh-CN/next/installation.html new file mode 100644 index 0000000000..13c9a3ce0a --- /dev/null +++ b/docs/zh-CN/next/installation.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

next

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/next/installation/index.html b/docs/zh-CN/next/installation/index.html new file mode 100644 index 0000000000..13c9a3ce0a --- /dev/null +++ b/docs/zh-CN/next/installation/index.html @@ -0,0 +1,141 @@ +Installation · Docusaurus

next

Translate

Installation

Docusaurus的初始设计就是要易于安装并让你的网站可以迅速运行。 To install Docusaurus, we have created an easy script that will get all of the infrastructure set up for you:

+
    +

  1. Ensure you have the latest version of Node installed. We also recommend you install Yarn as well.

    +
    +

    You have to be on Node >= 8.x and Yarn >= 1.5.

    +
    2. +

  2. 进入自己Github仓库的最上级目录，您将在这里创建文档。

    3. +

  3. npx docusaurus-init

    +
    +

    If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run yarn global add docusaurus-init or npm install --global docusaurus-init. After that, run docusaurus-init.

    +
    4. +
+

验证安装

+

Along with previously existing files and directories, your root directory will now contain a structure similar to:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+

Running the Docusaurus initialization script, docusaurus-init, produces a runnable, example website to base your site upon.

+
    +
  1. 在根目录中, 重命名 docs-examples-from-docusaurus 为 docs。
    2. +
  2. cd website
    3. +
  3. 重命名 blog-examples-from-docusaurus为 blog。
    4. +
  4. 通过 yarn start 或 npm start 运行本地服务器。
    5. +
  5. Load the example site at http://localhost:3000. You should see the example site loaded in your web browser. There's also a LiveReload server running and any changes made to the docs and files in the website directory will cause the page to refresh.
    6. +
+

+

Launching the server behind a proxy

+

If you are behind a corporate proxy, you need to disable it for the development server requests. It can be done using the NO_PROXY environment variable.

+
SET NO_PROXY=localhost
+yarn start (or npm run start)
+
+

Updating Your Docusaurus Version

+

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.
+
+
+

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

+
+

You can update to the latest version of Docusaurus by:

+
yarn upgrade docusaurus --latest
+
+

或

+
npm update docusaurus
+
+
+

If you are finding that you are getting errors after your upgrade, try to either clear your Babel cache (usually it's in a temporary directory or run the Docusaurus server (e.g., yarn start) with the BABEL_DISABLE_CACHE=1 environment configuration.

+
+
Site Preparation →
\ No newline at end of file diff --git a/docs/zh-CN/next/navigation.html b/docs/zh-CN/next/navigation.html new file mode 100644 index 0000000000..9838f620e3 --- /dev/null +++ b/docs/zh-CN/next/navigation.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

next

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/next/navigation/index.html b/docs/zh-CN/next/navigation/index.html new file mode 100644 index 0000000000..9838f620e3 --- /dev/null +++ b/docs/zh-CN/next/navigation/index.html @@ -0,0 +1,211 @@ +Navigation and Sidebars · Docusaurus

next

Translate

Navigation and Sidebars

Referencing Site Documents

+

If you want to reference another document in your docs directory (or the location you set via the optional customDocsPath path site configuration option), then you just use the name of the document you want to reference.

+

For example, if you are in doc2.md and you want to reference doc1.md:

+
I am referencing a [document](doc1.md).
+
+

How Documents are Linked

+

New markdown files within docs will show up as pages on the website. Links to those documents are created first by using the id in the header of each document. If there is no id field, then the name of the file will serve as the link name.

+

For example, creating an empty file such as docs/getting-started.md will enable the new page URL as /docs/getting-started.html.

+

Suppose you add this to your document:

+
---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
+

If you set the id field in the markdown header of the file, the doc will then be accessed from a URL of the form /docs/intro.html.

+
+

You need an id field to be able to add the document to the sidebar.

+
+

Adding Documents to a Sidebar

+

Many times, you will want to add a document to a sidebar that will be associated with one of the headers in the top navigation bar of the website. The most common sidebar, and the one that comes installed when Docusaurus is initialized, is the docs sidebar.

+
+

"docs" is just a name. It has no inherit meaning. You can change it as you wish.

+
+

You configure the contents of the sidebar, and the order of its documents, in the website/sidebars.json file.

+
+

Until you add your document to website/sidebars.json, they will only be accessible via a direct URL. The doc will not show up in any sidebar.

+
+

Within sidebars.json, add the id you used in the document header to existing sidebar/category. In the below case, docs is the name of the sidebar and Getting Started is a category within the sidebar.

+
{
+  "docs": {
+    "Getting Started": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

或者您也可以在边栏中创建一个新类别:

+
{
+  "docs": {
+    "My New Sidebar Category": [
+      "getting-started"
+    ],
+    ...
+  },
+  ...
+}
+
+

Adding New Sidebars

+

You can also put a document in a new sidebar. In the following example, we are creating an examples-sidebar sidebar within sidebars.json that has a category called My Example Category containing a document with an id of my-examples.

+
{
+  "examples-sidebar": {
+    "My Example Category": [
+      "my-examples"
+    ],
+    ...
+  },
+  ...
+}
+
+

It is important to note that until you add a document from the "examples-sidebar" sidebar to the nav bar, it will be hidden.

+

Additions to the Site Navigation Bar

+

To expose sidebars, you will add click-able 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: [
+    ...
+    { 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. 例如, 如果我们在 website/pages/help.js 中有一个页面, 我们可以通过添加以下链接来链接到它:

+
{
+  headerLinks: [
+    ...
+    { 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: [
+    ...
+    { 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.

+
+

若要在新选项卡中打开外部链接, 请在标题链接配置中提供 external: true 标志。

+
+

Site Navigation Bar Positioning

+

You have limited control where the search and languages dropdown elements are shown in the site navigation bar at the top of your website.

+

Search

+

如果你的网站上启用了搜索, 你的搜索栏会先显示在链接的右侧。 如果你想将搜索栏放在页眉中的链接之间, 请在 headerLinks 配置数组中添加搜索项:

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { search: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Languages Dropdown

+

如果您的网站上翻译功能启用了, 则 "语言" 下拉菜单将显示在链接的右侧 (如果启用了搜索功能, 就位于搜索栏的左侧)。 如果你想把语言选择下拉单放在页眉链接的中间，请添加一个语言项在 headerLinks 配置数组里：

+
{
+  headerLinks: [
+    { doc: 'foo', label: 'Foo' },
+    { languages: true },
+    { doc: 'bar', label: 'Bar' },
+  ],
+  ...
+}
+
+

Active Links In Site Navigation Bar

+

The links in the top navigation bar get siteNavItemActive and siteNavGroupActive class names to allow you to style the currently active link different from the others. siteNavItemActive is applied when there's an exact match between the navigation link and the currently displayed web page.

+
+

This does not include links of type href which are meant for external links only. If you manually set an href in your headerLinks to an internal page, document, or blog post, it will not get the siteNavItemActive class even if that page is being displayed.

+
+

The siteNavGroupActive class will be added to these links:

+
    +
  • doc links that belong to the same sidebar as the currently displayed document
    • +
  • The blog link when a blog post, or the blog listing page is being displayed
    • +
+

These are two separate class names so you can have the active styles applied to either exact matches only or a bit more broadly for docs that belong together. If you don't want to make this distinction you can add both classes to the same CSS rule.

+

Secondary On-Page Navigation

+

We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the onPageNav site configuration option to your siteConfig.js.

+
{
+  onPageNav: 'separate',
+  ...
+}
+
+

Currently, 'separate' is the only option available for this field. This provides a separate navigation on the right side of the page.

+
← Enabling SearchTranslations and Localization →
\ No newline at end of file diff --git a/docs/zh-CN/next/publishing.html b/docs/zh-CN/next/publishing.html new file mode 100644 index 0000000000..a9d1987301 --- /dev/null +++ b/docs/zh-CN/next/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

next

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/zh-CN/next/publishing/index.html b/docs/zh-CN/next/publishing/index.html new file mode 100644 index 0000000000..a9d1987301 --- /dev/null +++ b/docs/zh-CN/next/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

next

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/zh-CN/next/search.html b/docs/zh-CN/next/search.html new file mode 100644 index 0000000000..132627cb3e --- /dev/null +++ b/docs/zh-CN/next/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

next

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/next/search/index.html b/docs/zh-CN/next/search/index.html new file mode 100644 index 0000000000..132627cb3e --- /dev/null +++ b/docs/zh-CN/next/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

next

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/next/site-config.html b/docs/zh-CN/next/site-config.html new file mode 100644 index 0000000000..9cafc52a78 --- /dev/null +++ b/docs/zh-CN/next/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

next

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/next/site-config/index.html b/docs/zh-CN/next/site-config/index.html new file mode 100644 index 0000000000..9cafc52a78 --- /dev/null +++ b/docs/zh-CN/next/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

next

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/next/site-creation.html b/docs/zh-CN/next/site-creation.html new file mode 100644 index 0000000000..ea8336e2c2 --- /dev/null +++ b/docs/zh-CN/next/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

next

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/next/site-creation/index.html b/docs/zh-CN/next/site-creation/index.html new file mode 100644 index 0000000000..ea8336e2c2 --- /dev/null +++ b/docs/zh-CN/next/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

next

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/next/site-preparation.html b/docs/zh-CN/next/site-preparation.html new file mode 100644 index 0000000000..006f930d59 --- /dev/null +++ b/docs/zh-CN/next/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

next

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/next/site-preparation/index.html b/docs/zh-CN/next/site-preparation/index.html new file mode 100644 index 0000000000..006f930d59 --- /dev/null +++ b/docs/zh-CN/next/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

next

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/next/translation.html b/docs/zh-CN/next/translation.html new file mode 100644 index 0000000000..3de0594781 --- /dev/null +++ b/docs/zh-CN/next/translation.html @@ -0,0 +1,265 @@ +Translations and Localization · Docusaurus

next

Translate

Translations and Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/next/translation/index.html b/docs/zh-CN/next/translation/index.html new file mode 100644 index 0000000000..3de0594781 --- /dev/null +++ b/docs/zh-CN/next/translation/index.html @@ -0,0 +1,265 @@ +Translations and Localization · Docusaurus

next

Translate

Translations and Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/next/versioning.html b/docs/zh-CN/next/versioning.html new file mode 100644 index 0000000000..2878edd763 --- /dev/null +++ b/docs/zh-CN/next/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

next

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/next/versioning/index.html b/docs/zh-CN/next/versioning/index.html new file mode 100644 index 0000000000..2878edd763 --- /dev/null +++ b/docs/zh-CN/next/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

next

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/publishing.html b/docs/zh-CN/publishing.html new file mode 100644 index 0000000000..f36450ae22 --- /dev/null +++ b/docs/zh-CN/publishing.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/zh-CN/publishing/index.html b/docs/zh-CN/publishing/index.html new file mode 100644 index 0000000000..f36450ae22 --- /dev/null +++ b/docs/zh-CN/publishing/index.html @@ -0,0 +1,256 @@ +Publishing your site · Docusaurus

1.3.1

Translate

Publishing your site

You should now have a site up and running locally. Once you have customized it to your liking, it's time to publish it. Docusaurus generates a static HTML website that is ready to be served by your favorite web server or online hosting solution.

+

Building Static HTML Pages

+

To create a static build of your website, run the following script from the website directory:

+
yarn run build # or `npm run build`
+
+

This will generate a build directory inside the website directory containing the .html files from all of your docs and other pages included in pages.

+

Hosting Static HTML Pages

+

At this point, you can grab all of the files inside the website/build directory and copy them over to your favorite web server's html directory.

+
+

For example, both Apache and nginx serve content from /var/www/html by default. That said, choosing a web server or provider is outside the scope of Docusaurus.

+

When serving the site from your own web server, ensure the web server is serving the asset files with the proper HTTP headers. CSS files should be served with the content-type header of text/css. In the case of nginx, this would mean setting include /etc/nginx/mime.types; in your nginx.conf file. See this issue for more info.

+
+

Hosting on a Service:

+ +

Using GitHub Pages

+

While choosing a web server or host is outside Docusaurus' scope, Docusaurus was designed to work really well with one of the most popular hosting solutions for open source projects: GitHub Pages.

+

Deploying your Docusaurus site to GitHub Pages is straightforward if you are already using GitHub to host your project. Your code repository does not even need to be public.

+
+

Even if your repository is private, anything published to a gh-pages branch will be public.

+
+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ + + + + + + + +
NameDescription
organizationNameThe GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
projectNameThe name of the GitHub repository for your project. For example, Docusaurus is hosted at https://github.com/facebook/docusaurus, so our project name in this case would be "docusaurus".
+
+

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:

+ + + + + + + +
NameDescription
GIT_USERThe username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your own GitHub username.
+

There are also two optional parameters that are set as environment variables:

+ + + + + + + + +
NameDescription
USE_SSHIf this is set to true, then SSH is used instead of HTTPS for the connection to the GitHub repo. HTTPS is the default if this variable is not set.
CURRENT_BRANCHThe branch that contains the latest docs changes that will be deployed. Usually, the branch will be master, but it could be any branch (default or otherwise) except for gh-pages. If nothing is set for this variable, then the current branch will be used.
+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate. If you run into issues related to SSH keys, visit GitHub's authentication documentation.

+
GIT_USER=<GIT_USER> \
+  CURRENT_BRANCH=master \
+  USE_SSH=true \
+  yarn run publish-gh-pages # or `npm run publish-gh-pages`
+
+
+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

+
+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://username.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://facebook.github.io/Docusaurus (it can also be accessed via https://docusaurus.io/), because it is served from the gh-pages branch of the https://github.com/facebook/docusaurus GitHub repository. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

+

However, you can automate the publishing process with continuous integration (CI).

+

Automating Deployments Using Continuous Integration

+

Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the publish-gh-pages script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.

+

Using Circle CI 2.0

+

If you haven't done so already, you can setup CircleCI for your open source project. Afterwards, in order to enable automatic deployment of your site and documentation via CircleCI, just configure Circle to run the publish-gh-pages script as part of the deployment step. You can follow the steps below to get that setup.

+
    +
  1. Ensure the GitHub account that will be set as the GIT_USER has write access to the repository that contains the documentation, by checking Settings | Collaborators & teams in the repository.
    2. +
  2. Log into GitHub as the GIT_USER.
    3. +
  3. Go to https://github.com/settings/tokens for the GIT_USER and generate a new personal access token, granting it full control of private repositories through the repository access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.
    4. +
  4. Open your Circle CI dashboard, and navigate to the Settings page for your repository, then select "Environment variables". The URL looks like https://circleci.com/gh/ORG/REPO/edit#env-vars, where "ORG/REPO" should be replaced with your own GitHub organization/repository.
    5. +
  5. Create a new environment variable named GITHUB_TOKEN, using your newly generated access token as the value.
    6. +
  6. Create a .circleci directory and create a config.yml under that directory.
    7. +
  7. Copy the text below into .circleci/config.yml.
    8. +
+
# If you only want circle to run on direct commits to master, you can uncomment this out
+# and uncomment the filters: *filter-only-master down below too
+#
+# aliases:
+#  - &filter-only-master
+#    branches:
+#      only:
+#        - master
+
+version: 2
+jobs:
+  deploy-website:
+    docker:
+      # specify the version you desire here
+
+      - image: circleci/node:8.11.1
+
+    steps:
+
+      - checkout
+      - run:
+          name: Deploying to GitHub Pages
+          command: |
+            git config --global user.email "<GITHUB_USERNAME>@users.noreply.github.com"
+            git config --global user.name "<YOUR_NAME>"
+            echo "machine github.com login <GITHUB_USERNAME> password $GITHUB_TOKEN" > ~/.netrc
+            cd website && yarn install && GIT_USER=<GIT_USER> yarn run publish-gh-pages
+
+workflows:
+  version: 2
+  build_and_deploy:
+    jobs:
+
+      - deploy-website:
+#         filters: *filter-only-master
+
+

Make sure to replace all <....> in the command: sequence with appropriate values. For <GIT_USER>, it should be a GitHub account that has access to push documentation to your GitHub repository. Many times <GIT_USER> and <GITHUB_USERNAME> will be the same.

+

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

+
+

If you want to use SSH for your GitHub repository connection, you can set USE_SSH=true. So the above command would look something like: cd website && npm install && GIT_USER=<GIT_USER> USE_SSH=true npm run publish-gh-pages.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the value of CURRENT_BRANCH is already defined as an environment variable within CircleCI and will be picked up by the script automatically.

+
+

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+
+

If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.

+
+

Tips & Tricks

+

When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:

+
# Circle CI 2.0 Config File
+# This config file will prevent tests from being run on the gh-pages branch.
+version: 2
+jobs:
+  build:
+    machine: true
+    branches:
+      ignore: gh-pages
+    steps:
+      - run: echo "Skipping tests on gh-pages branch"
+
+

Save this file as config.yml and place it in a .circleci directory inside your website/static directory.

+

Using Travis CI

+
    +
  1. Go to https://github.com/settings/tokens and generate a new personal access token
    2. +
  2. Using your GitHub account, add the Travis CI app to the repository you want to activate.
    3. +
  3. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the More options > Setting > Environment Variables section of your repository.
    4. +
  4. Create a new environment variable named GH_TOKEN with your newly generated token as its value, then GH_EMAIL (your email address) and GH_NAME (your GitHub username).
    5. +
  5. Create a .travis.yml on the root of your repository with below text.
    6. +
+
# .travis.yml
+language: node_js
+node_js:
+  - '8'
+branches:
+  only:
+    - master
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - cd website && yarn install && GIT_USER="${GH_NAME}" yarn run publish-gh-pages
+
+

Now, whenever a new commit lands in master, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.

+

Hosting on Netlify

+

Steps to configure your Docusaurus-powered site on Netlify.

+
    +

  1. Select New site from Git

    2. +

  2. Connect to your preferred Git provider.

    3. +

  3. Select the branch to deploy. Default is master

    4. +

  4. Configure your build steps:

    +
      +
    • For your build command enter: cd website; npm install; npm run build;
      • +
    • For publish directory: website/build/<projectName> (use the projectName from your siteConfig)
      • +
    5. +

  5. Click Deploy site

    6. +
+

You can also configure Netlify to rebuild on every commit to your repository, or only master branch commits.

+

Publishing to GitHub Enterprise

+

GitHub enterprise installations should work in the same manner as github.com; you only need to identify the organization's GitHub Enterprise host.

+ + + + + + + +
NameDescription
GITHUB_HOSTThe hostname for the GitHub enterprise server.
+

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

+
← Creating your siteAdding a Blog →
\ No newline at end of file diff --git a/docs/zh-CN/search.html b/docs/zh-CN/search.html new file mode 100644 index 0000000000..1283bcc8ad --- /dev/null +++ b/docs/zh-CN/search.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.1

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/search/index.html b/docs/zh-CN/search/index.html new file mode 100644 index 0000000000..1283bcc8ad --- /dev/null +++ b/docs/zh-CN/search/index.html @@ -0,0 +1,108 @@ +Enabling Search · Docusaurus

1.3.1

Translate

Enabling Search

Docusaurus支持使用 Algolia DocSearch 来搜索你的网站。 Once your website is online, you can submit it to DocSearch. Algolia will then send you credentials you can add to your siteConfig.js.

+

DocSearch works by crawling the content of your website every 24 hours and putting all the content in an Algolia index. This content is then queried directly from your front-end using the Algolia API. Note that your website need to be publicly available for this to work (ie. not behind a firewall). This service is free.

+

启用搜索框

+

Enter your API key and index name (sent by Algolia) into siteConfig.js in the algolia section to enable search for your site.

+
const siteConfig = {
+  ...
+  algolia: {
+    apiKey: 'my-api-key',
+    indexName: 'my-index-name',
+    algoliaOptions: {} // Optional, if provided by Algolia
+  },
+  ...
+};
+
+

Extra Search Options

+

You can also specify extra search options used by Algolia by using an algoliaOptions field in algolia. 如果您想为不同版本或语言的文档提供不同的搜索结果，这可能会很有用。 Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be found here.

+
const siteConfig = {    
+  ...   
+  algolia: {    
+    ... 
+    algoliaOptions: {   
+      facetFilters: [ "lang:LANGUAGE", "version:VERSION" ] 
+    }   
+  },    
+};  
+
+

Algolia might provide you with extra search options. If so, you should add them to the algoliaOptions object.

+

Controlling the Location of the Search Bar

+

By default, the search bar will be the rightmost element in the top navigation bar.

+

If you want to change the default location, add the searchBar flag in the headerLinks field of siteConfig.js in your desired location. For example, you may want the search bar between your internal and external links.

+
const siteConfig = {
+  ...
+  headerLinks: [
+    {...}
+    {...}
+    { search: true }
+    {...}
+    {...}
+  ],
+  ...
+};
+
+

Disabling the Search Bar

+

To disable the search bar, comment out (recommended) or delete the algolia section in the siteConfig.js file.

+

Also, if you have customized the location of the search bar in headerLinks, set search: false.

+
← Custom PagesNavigation and Sidebars →
\ No newline at end of file diff --git a/docs/zh-CN/site-config.html b/docs/zh-CN/site-config.html new file mode 100644 index 0000000000..9445f8605b --- /dev/null +++ b/docs/zh-CN/site-config.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.1

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/site-config/index.html b/docs/zh-CN/site-config/index.html new file mode 100644 index 0000000000..9445f8605b --- /dev/null +++ b/docs/zh-CN/site-config/index.html @@ -0,0 +1,258 @@ +siteConfig.js · Docusaurus

1.3.1

Translate

siteConfig.js

网站配置的很大一部分是通过编辑 siteConfig 文件来完成的。

+

用户展示

+

数组users用于存储要在网站上显示的所有项目或用户信息。 当前提供的示例 pages/en/index.js 和 pages/en/users.js 文件中有用到这个属性。 每个user对象都包含有 caption、image、infoLink和 pinned 属性。 caption 是当有人悬停在该用户头像(image) 上时显示的文本, 而 infoLink 是点击头像后将要跳转的用户信息链接。 pinned 表示是否在首页固定显示。

+

目前数组users只用于示例文件index.js 和 users.js中。 如果你不想要用户展示页面或不想在首页展示用户，你可以删除它。

+

siteConfig 属性

+

siteConfig 对象包含了网站的大部分配置。

+

必填属性

+

baseUrl - 网站的baseUrl。

+

colors - 网站的颜色。

+
    +
  • primaryColor 标题导航栏和侧边栏的颜色。
    • +
  • secondaryColor 当网站窗口收缩 (包括手机) 时标题导航栏第二行中看到的颜色。
    • +
  • 还可以添加自定义颜色。 例如, 如果添加自定义样式时要用特定的 $myColor颜色, 则将 myColor 字段添加到 colors ，就可以轻松完成配置。
    • +
+

copyright - 网站页脚和信息流中的版权声明。

+

favicon - URL for site favicon.

+

headerIcon - URL for icon used in header navigation bar.

+

headerLinks - Links that will be used in the header navigation bar. The label field of each object will be the link text and will also be translated for each language.

+

示例用法：

+
headerLinks: [
+  // Links to document with id doc1 for current language/version
+  { doc: "doc1", label: "Getting Started" },
+  // Link to page found at pages/en/help.js or if that does not exist, pages/help.js, for current language
+  { page: "help", label: "Help" },
+  // Links to href destination
+  { href: "https://github.com/", label: "GitHub" },
+  // Links to blog generated by Docusaurus (${baseUrl}blog)
+  { blog: true, label: "Blog" },
+  // Determines search bar position among links
+  { search: true },
+  // Determines language drop down position among links
+  { languages: true }
+],
+
+

noIndex - 真值。 如果为true， 这是通过header标签来完成的，因此只会影响文档和页面。 我们并不会尝试隐藏静态资源， 只能尽力而为， 因为恶意爬虫仍可以索引您的站点。

+

organizationName - GitHub username of the organization or user hosting this project. This is used by the publishing script to determine where your GitHub pages website will be hosted.

+

projectName - Project name. This must match your GitHub repository project name (case-sensitive).

+

tagline - 网站标语。

+

title - 网站标题。

+

url - URL for your website.

+

可选属性

+

algolia - Information for Algolia search integration. If this field is excluded, the search bar will not appear in the header. You must specify two values for this field, and one (appId) is optional.

+
    +
  • apiKey - the Algolia provided API key for your search.
    • +
  • indexName - the Algolia provided index name for your search (usually this is the project name)
    • +
  • appId - Algolia provides a default scraper for your docs. If you provide your own, you will probably get this id from them.
    • +
+

blogSidebarCount - Control the number of blog posts that show up in the sidebar. See the adding a blog docs for more information.

+

blogSidebarTitle - Control the title of the blog sidebar. See the adding a blog docs for more information.

+

cleanUrl - If true, allow URLs with no html extension. For example, a request to URL https://docusaurus.io/docs/installation will returns the same result as https://docusaurus.io/docs/installation.html.

+

cname - The CNAME for your website. It will go into a CNAME file when your site is built.

+

customDocsPath - By default, Docusaurus expects your documentation to be in a directory called docs. This directory is at the same level as the website directory (i.e., not inside the website directory). You can specify a custom path to your documentation with this field.

+
customDocsPath: 'docs/site';
+
+
customDocsPath: 'website-docs';
+
+

defaultVersionShown - The default version for the site to be shown. If this is not set, the latest version will be shown.

+

disableHeaderTitle - An option to disable showing the title in the header next to the header icon. Exclude this field to keep the header as normal, otherwise set to true.

+

disableTitleTagline - An option to disable showing the tagline in the title of main pages. Exclude this field to keep page titles as Title • Tagline. Set to true to make page titles just Title.

+

editUrl - URL for editing docs, usage example: editUrl + 'en/doc1.md'. If this field is omitted, there will be no "Edit this Doc" button for each document.

+

facebookAppId - If you want Facebook Like/Share buttons in the footer and at the bottom of your blog posts, provide a Facebook application id.

+

facebookComments - Set this to true if you want to enable Facebook comments at the bottom of your blog post. facebookAppId has to be also set.

+

facebookPixelId - Facebook Pixel ID to track page views.

+

fonts - Font-family CSS configuration for the site. If a font family is specified in siteConfig.js as $myFont, then adding a myFont key to an array in fonts will allow you to configure the font. Items appearing earlier in the array will take priority of later elements, so ordering of the fonts matter.

+

In the below example, we have two sets of font configurations, myFont and myOtherFont. Times New Roman is the preferred font in myFont. -apple-system is the preferred in myOtherFont.

+
fonts: {
+  myFont: [
+    'Times New Roman',
+    'Serif'
+  ],
+  myOtherFont: [
+    '-apple-system',
+    'system-ui'
+  ]
+},
+
+

The above fonts would be represented in your CSS file(s) as variables $myFont and $myOtherFont.

+
h1 {
+  font-family: $myFont;
+}
+
+

footerIcon - URL for a footer icon. Currently used in the core/Footer.js file provided as an example, but it can be removed from that file.

+

gaTrackingId - Google Analytics tracking ID to track page views.

+

gaGtag - Set this to true if you want to use global site tags (gtag.js) for Google analytics instead of analytics.js.

+

githubHost - Hostname of your server. Useful if you are using GitHub Enterprise.

+

highlight - Syntax highlighting options:

+
    +
  • theme is the name of the theme used by Highlight.js when highlighting code. You can find the list of supported themes here.
    • +
  • version specifies a particular version of Highlight.js to be used.
    • +
  • hljs provides an escape valve by passing an instance of Highlight.js to the function specified here, allowing additional languages to be registered for syntax highlighting.
    • +
  • defaultLang defines a default language. It will be used if one is not specified at the top of the code block. You can find the list of supported languages here.
    • +
  • themeUrl is the custom URL of CSS theme file that you want to use with Highlight.js. If this is provided, the theme and version fields will be ignored.
    • +
+

markdownPlugins - An array of plugins to be loaded by Remarkable, the markdown parser and renderer used by Docusaurus. The plugin will receive a reference to the Remarkable instance, allowing custom parsing and rendering rules to be defined.

+

ogImage - Local path to an Open Graph image (e.g., img/myImage.png). This image will show up when your site is shared on Facebook and other websites/apps where the Open Graph protocol is supported.

+

onPageNav - If you want a visible navigation option for representing topics on the current page. Currently, there is one accepted value for this option:

+ +

scripts - Array of JavaScript sources to load. The script tag will be inserted in the HTML head.

+

separateCss - Directories inside which any css files will not be processed and concatenated to Docusaurus' styles. This is to support static html pages that may be separate from Docusaurus with completely separate styles.

+

scrollToTop - Set this to true if you want to enable the scroll to top button at the bottom of your site.

+

scrollToTopOptions - Optional options configuration for the scroll to top button. You do not need to use this, even if you set scrollToTop to true; it just provides you more configuration control of the button. You can find more options here. By default, we set the zIndex option to 100.

+

stylesheets - Array of CSS sources to load. The link tag will be inserted in the HTML head.

+

translationRecruitingLink - URL for the Help Translate tab of language selection when languages besides English are enabled. This can be included you are using translations but does not have to be.

+

twitter - Set this to true if you want a Twitter social button to appear at the bottom of your blog posts.

+

twitterUsername - If you want a Twitter follow button at the bottom of your page, provide a Twitter username to follow. For example: docusaurus.

+

twitterImage - Local path to your Twitter card image (e.g., img/myImage.png). This image will show up on the Twitter card when your site is shared on Twitter.

+

useEnglishUrl - If you do not have translations enabled (e.g., by having a languages.js file), but still want a link of the form /docs/en/doc.html (with the en), set this to true.

+

users - The users array mentioned earlier.

+

usePrism - Array of languages to use Prism syntax highlighter. Refer to Using Prism as additional syntax highlighter. Set it to true to use Prism on all languages.

+

wrapPagesHTML - Boolean flag to indicate whether html files in /pages should be wrapped with Docusaurus site styles, header and footer. This feature is experimental and relies on the files being html fragments instead of complete pages. It inserts the contents of your html file with no extra processing. Defaults to false.

+

Users can also add their own custom fields if they wish to provide some data across different files.

+

Example siteConfig.js with many available fields

+
const users = [
+  {
+    caption: 'User1',
+    image: '/test-site/img/docusaurus.svg',
+    infoLink: 'https://www.example.com',
+    pinned: true,
+  },
+];
+
+const siteConfig = {
+  title: 'Docusaurus',
+  tagline: 'Generate websites!',
+  url: 'https://docusaurus.io',
+  baseUrl: '/',
+  // For github.io type URLS, you would combine the URL and baseUrl like:
+  // url: 'https://reasonml.github.io',
+  // baseUrl: '/reason-react/',
+  defaultVersionShown: '1.0.0',
+  organizationName: 'facebook',
+  projectName: 'docusaurus',
+  noIndex: false,
+  // For no header links in the top nav bar -> headerLinks: [],
+  headerLinks: [
+    {doc: 'doc1', label: 'Docs'},
+    {page: 'help', label: 'Help'},
+    {search: true},
+    {blog: true},
+  ],
+  headerIcon: 'img/docusaurus.svg',
+  favicon: 'img/favicon.png',
+  colors: {
+    primaryColor: '#2E8555',
+    secondaryColor: '#205C3B',
+  },
+  editUrl: 'https://github.com/facebook/docusaurus/edit/master/docs/',
+  // Users variable set above
+  users,
+  disableHeaderTitle: true,
+  disableTitleTagline: true,
+  separateCss: ['static/css/non-docusaurus', 'static/assets/separate-css'],
+  footerIcon: 'img/docusaurus.svg',
+  translationRecruitingLink: 'https://crowdin.com/project/docusaurus',
+  algolia: {
+    apiKey: '0f9f28b9ab9efae89810921a351753b5',
+    indexName: 'github',
+  },
+  gaTrackingId: 'UA-12345678-9',
+  highlight: {
+    theme: 'default',
+  },
+  markdownPlugins: [
+    function foo(md) {
+      md.renderer.rules.fence_custom.foo = function(
+        tokens,
+        idx,
+        options,
+        env,
+        instance
+      ) {
+        return '<div class="foo">bar</div>';
+      };
+    },
+  ],
+  scripts: ['https://docusaurus.io/slash.js'],
+  stylesheets: ['https://docusaurus.io/style.css'],
+  facebookAppId: '1615782811974223',
+  facebookComments: true,
+  facebookPixelId: '352490515235776',
+  twitter: 'true',
+  twitterUsername: 'docusaurus',
+  twitterImage: 'img/docusaurus.png',
+  ogImage: 'img/docusaurus.png',
+  cleanUrl: true,
+  scrollToTop: true,
+  scrollToTopOptions: {
+    zIndex: 100,
+  },
+};
+
+module.exports = siteConfig;
+
+
← Pages and Styles
\ No newline at end of file diff --git a/docs/zh-CN/site-creation.html b/docs/zh-CN/site-creation.html new file mode 100644 index 0000000000..91157afadd --- /dev/null +++ b/docs/zh-CN/site-creation.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/site-creation/index.html b/docs/zh-CN/site-creation/index.html new file mode 100644 index 0000000000..91157afadd --- /dev/null +++ b/docs/zh-CN/site-creation/index.html @@ -0,0 +1,139 @@ +Creating your site · Docusaurus

1.3.1

Translate

Creating your site

Docusaurus was created to hopefully make it super simple for you to create a site and documentation for your open source project.

+

After installation and preparation, much of the work to create a basic site for your docs is already complete.

+

Site Structure

+

Your site structure looks like the following:

+
root-directory
+├── docs
+└── website
+    ├── blog
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

This assumes that you removed the example .md files that were installed with the initialization script.

+
+

All of your documentation files should be placed inside the docs directory as markdown .md files. Any blog posts should be inside the blog directory.

+
+

The blog posts must be formatted as YYYY-MM-DD-your-file-name.md

+
+

Create Your Basic Site

+

To create a fully functional site, you only need to do a few steps:

+
    +

  1. Add your documentation to the /docs directory as .md files, ensuring you have the proper header in each file. The simplest header would be the following, where id is the link name (e.g., docs/intro.html) and the title, is, of course, the title of the browser page.

    +
    ---
+id: intro
+title: Getting Started
+---
+
+My new content here..
+
    2. +

  2. Add zero or more docs to the sidebars.json file so that your documentation is rendered in a sidebar, if you choose them to be.

    3. +
+
+

If you do not add your documentation to the sidebars.json file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

+
+
    +
  1. Modify the website/siteConfig.js file to configure your site, following the comments included in the docs and the website/siteConfig.js to guide you.
    2. +
  2. Create any custom pages and/or customize the website/core/Footer.js file that provides the footer for your site.
    3. +
  3. Place assets, such as images, in the website/static/ directory.
    4. +
  4. Run the site to see the results of your changes.
    5. +
+
cd website
+yarn run start # or `npm run start`
+# Navigate to http://localhost:3000
+
+

Special Customization

+

Docs Landing Page

+

If you prefer to have your landing page be straight to your documentation, you can do this through a redirect.

+
    +
  1. Remove the index.js file from the website/pages directory, if it exists.
    2. +
  2. Add a custom static index.html page in the website/static directory with the following contents:
    3. +
+
<!DOCTYPE HTML>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=docs/id-of-doc-to-land-on.html">
+    <script type="text/javascript">
+      window.location.href = 'docs/id-of-doc-to-land-on.html';
+    </script>
+    <title>Your Site Title Here</title>
+  </head>
+  <body>
+    If you are not redirected automatically, follow this <a href="docs/id-of-doc-to-land-on.html">link</a>.
+  </body>
+</html>
+
+
+

You will get the id of the document to land on the .md metadata of that doc page.

+
+

Blog Only

+

You can also use Docusaurus to host your blog only.

+
← Site PreparationPublishing your site →
\ No newline at end of file diff --git a/docs/zh-CN/site-preparation.html b/docs/zh-CN/site-preparation.html new file mode 100644 index 0000000000..b7223a8ffa --- /dev/null +++ b/docs/zh-CN/site-preparation.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.1

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/site-preparation/index.html b/docs/zh-CN/site-preparation/index.html new file mode 100644 index 0000000000..b7223a8ffa --- /dev/null +++ b/docs/zh-CN/site-preparation/index.html @@ -0,0 +1,101 @@ +Site Preparation · Docusaurus

1.3.1

Translate

Site Preparation

在 安装 Docusaurus之后, 您现在有了一个特定网站的可用骨架。 下面将讨论 Docusaurus 结构的其余部分, 以便您准备建站。

+

目录结构

+

正如安装 Docusaurus后所示, 初始化脚本创建了一个类似于以下内容的目录结构:

+
root-directory
+├── docs-examples-from-docusaurus
+│   ├── doc1.md
+│   ├── doc2.md
+│   ├── doc3.md
+│   ├── exampledoc4.md
+│   └── exampledoc5.md
+└── website
+    ├── blog-examples-from-docusaurus
+    │   ├── 2016-03-11-blog-post.md
+    │   ├── 2017-04-10-blog-post-two.md
+    │   ├── 2017-09-25-testing-rss.md
+    │   ├── 2017-09-26-adding-rss.md
+    │   └── 2017-10-24-new-version-1.0.0.md
+    ├── core
+    │   └── Footer.js
+    ├── package.json
+    ├── pages
+    ├── sidebars.json
+    ├── siteConfig.js
+    └── static
+
+
+

You may have already renamed the example blog (website/blog-examples-from-docusaurus) and document (docs-examples-from-docusaurus) directories when you verified the installation.

+
+
    +
  • website/core/Footer.js文件是一个React组件，它充当由Docusaurus生成站点的页脚，同时应由用户自己来定制。
    • +
  • The website/blog-examples-from-docusaurus directory contains examples of blog posts written in markdown.
    • +
  • The docs-examples-from-docusaurus directory contains example documentation files written in markdown.
    • +
  • The website/pages directory contains example top-level pages for the site.
    • +
  • The website/static directory contains static assets used by the example site.
    • +
  • website/siteConfig.js 文件是 Docusaurus 使用的主要配置文件。
    • +
+

您不能删除 website/siteConfig.js 和 website/core/Footer.js 文件, 但可以按您的意愿编辑它们。

+

You should keep the website/pages and website/static directories, but may change the content inside them as you wish. 在 website/pages 目录，你至少应该有一个 en/index.js 或 en/index.html 以及在website/static里有一个图片作为您的页眉图标(header icon) 。

+
← InstallationCreating your site →
\ No newline at end of file diff --git a/docs/zh-CN/translation.html b/docs/zh-CN/translation.html new file mode 100644 index 0000000000..1c8b05bc16 --- /dev/null +++ b/docs/zh-CN/translation.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/translation/index.html b/docs/zh-CN/translation/index.html new file mode 100644 index 0000000000..1c8b05bc16 --- /dev/null +++ b/docs/zh-CN/translation/index.html @@ -0,0 +1,265 @@ +Translations & Localization · Docusaurus

1.3.1

Translate

Translations & Localization

Docusaurus allows for easy translation functionality using Crowdin. 用英文写的文档文件会被上传到 Crowdin, 供社区内的用户翻译。 用英文字符串编写的顶级网页可以通过在<translate>标记中打包任何要翻译的字符串来进行翻译。 其他标题和标签也会被发现和正确翻译。

+

Docusaurus 翻译配置

+

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

+
npm 运行示例翻译
+
+

或

+
yarn运行示例翻译
+
+

这会创建以下文件:

+
pages/en/help-with-translations.js
+languages.js
+../crowdin.yaml
+
+
    +
  • pages/en/help-with-translations.js 文件包括由 examples 脚本生成的相同的初学者帮助页, 但是现在也包括翻译标记。
    • +
+
+

Generally, you will use help-with-translations.js as a guide to enable translations in your other pages, but not actually commit the file to your repo (i.e., you can delete it). However, if you want a Help page, and you currently do not have one, you can rename this file to help.js and use it as a starting point.

+
+
    +

  • The languages.js file tells Docusaurus what languages you want to enable for your site. By default, we expect English to be enabled.

    • +

  • The crowdin.yaml file is used to configure Crowdin integration, and is copied up one level into your Docusaurus project repo. If your Docusaurus project resides in /project/website, then crowdin.yaml will be copied to /project/crowdin.yaml.

    • +
+

翻译现有文档

+

Your documentation files (e.g., the .md files that live in your docs directory) do not need to be changed or moved to support translations. They will be uploaded to Crowdin to be translated directly.

+

在页面上启用翻译

+

页面允许您自定义页面设计和特定内容, 就像一个自定义索引页或帮助页。

+

Pages with text that you want translated should be placed in website/pages/en directory.

+

把你需要翻译的字符串打包到 <translate> 标签中，然后添加 require 声明到文件的顶部。

+
...
+const translate = require('../../server/translate.js').translate;
+...
+<h2>
+  <translate>This header will be translated</translate>
+</h2>
+...
+
+

您还可以提交一个可选说明属性, 以便为翻译人员提供有关如何翻译字符串的更多详情:

+
<p>
+  <translate desc="flower, not verb">Rose</translate>
+<p>
+
+
+

The <translate> tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation> tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate> tags amongst the pure substrings of that string.

+
+

收集字符串以进行转换

+

有本地化页面的字符串必须提取出并提供给Crowdin。

+

Add the following script to your website/package.json file, if it does not exist already:

+
{
+  ...
+  "scripts": {
+    "write-translations": "docusaurus-write-translations"
+  },
+  ...
+}
+
+

运行该脚本将生成一个 website/i18n/en.json 文件, 其中包含将从英语翻译成其他语言的所有字符串。

+

该脚本将包含在以下位置的文本:

+
    +
  • title 和 sidebar_label 在markdown标题中的字符串
    • +
  • sidebars. json 中的种类名称
    • +
  • 在siteConfig.js中的标语
    • +
  • siteConfig 里的标题链接 label 字符串
    • +
  • 在 pages 中的任何 . js 文件中, 在 < translate > 标记中包装的字符串
    • +
+

Custom Translation Strings

+

If you want to add additional custom translation strings, or override any of the strings that get produced by the script that creates the website/i18n/en.json file, you can add a website/data/custom-translation-strings.json file. The file should have form of:

+
{
+  "localized-strings": {
+    "id": "string",
+    "id2": "string2"
+  },
+  "pages-strings" : {
+    "id3": "string3",
+    "id4": "string4"
+  }
+}
+
+

where localized-strings represent strings in your documentation content and pages-strings represents metadata in your documentation (e.g., title, links, etc).

+

Here is an example:

+
{
+  "_comment": "This file is used to provide custom strings for translations, including overriding defaults",
+  "localized-strings": {
+    "translation": "Translations and Localization"
+  },
+  "pages-strings" : {
+        "Help Translate|recruit community translators for your project": "Help Us Translate"
+  }
+}
+
+

See the generated website/i18n/en.json for an example.

+

字符串是怎么转换的

+

Docusaurus本身并不会做任何翻译工作 相反, 它集成了 crowdin 来上传需翻译的文字, 然后从 crowdin 下载适当的翻译文件。

+

Docusaurus怎样使用字符串翻译

+

这部分提供Docusaurus中的翻译是怎么工作的上下文

+

字符串

+

Docusaurus站点有许多需要本地化处理的字符串。 但是, 维护一个通过站点使用的字符串列表可能会很辛苦。 Docusaurus simplifies this by centralizing strings.

+

The header navigation, for example can have links to 'Home' or your 'Blog'. This and other strings found in the headers and sidebars of pages are extracted and placed into i18n/en.json. When your files are translated, say into Spanish, a i18n/es-ES.json file will be downloaded from Crowdin. Then, when the Spanish pages are generated, Docusaurus will replace the English version of corresponding strings with translated strings from the corresponding localized strings file (e.g. In a Spanish enabled site 'Help' will become 'Ayuda').

+

Markdown Files

+

For documentation files themselves, translated versions of these files are downloaded and then rendered through the proper layout template.

+

Other Pages

+

For other pages, Docusaurus will automatically transform all <translate> tags it finds into function calls that return the translated strings from the corresponding localized file locale.json.

+

Crowdin

+

Crowdin is a company that provides translation services. For Open Source projects, Crowdin provides free string translations.

+

Create your translation project on Crowdin. You can use Crowdin's guides to learn more about the translations work flow. We suggest that you deselect and do not include "English" as a translatable language to prevent the creation of en-US localization files as this can lead to confusion.

+
+

Ensure in your Crowdin settings, in the Translations section, that "Duplicate Strings" are set to "Hide - all duplicates will share the same translation". This setting will ensure that identical strings between versions share a single translation.

+
+

Your project will need a crowdin.yaml file generated. If you ran yarn examples translations or npm run examples translations, this file was created for you on the same level as your website directory.

+
+

You will need to install the crowdin command line interface. Please follow the installation directions.

+
+

The example below can be automatically generated by the Docusaurus cli with the examples script. It should be placed in the top level of your project directory to configure how and what files are uploaded/downloaded.

+

Below is an example Crowdin configuration for the respective languages: German, Spanish, French, Japanese, Korean, Bahasa Indonesia, Portuguese Brazilian, Chinese Simplified, and Chinese Traditional.

+
project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
+api_key_env: CROWDIN_DOCUSAURUS_API_KEY
+base_path: "./"
+preserve_hierarchy: true
+
+files:
+  -
+    source: '/docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: &anchor
+      locale:
+        'de': 'de'
+        'es-ES': 'es-ES'
+        'fr': 'fr'
+        'ja': 'ja'
+        'ko': 'ko'
+        'mr': 'mr-IN'
+        'pt-BR': 'pt-BR'
+        'zh-CN': 'zh-CN'
+        'zh-TW': 'zh-TW'
+
+

You can go here to learn more about customizing your crowdin.yaml file.

+

Setup the Crowdin Scripts

+

You will want to manually sync your files to and from Crowdin. The sync process will upload any markdown files in /docs as well as translatable strings in website/i18n/en.json. (These strings can be generated by running yarn write-translations.)

+

You can add the following to your package.json to manually trigger Crowdin.

+
"scripts": {
+  "crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
+  "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+},
+
+

Manual File Sync

+

You will always want to upload your markdown files and translatable strings first and the download the translations section. So run the commands in this order:

+
CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-upload
+CROWDIN_DOCUSAURUS_PROJECT_ID=YOUR_CROWDIN_PROJECT_ID CROWDIN_DOCUSAURUS_API_KEY=YOUR_CROWDIN_API_KEY yarn run crowdin-download
+
+
+

YOUR_CROWDIN_PROJECT_ID is the name of your Crowdin project. e.g., for https://crowdin.com/project/docusaurus/, that variable would be set to docusaurus. YOUR_CROWDIN_API_KEY is a unique key that is like a password. You can find it in the API tab of your Crowdin project's Settings.

+

These commands require having an environment variable set with your Crowdin project id and api key (CROWDIN_PROJECT_ID, CROWDIN_API_KEY). You can preface them inline as done above or add them permanently to your .bashrc or .bash_profile.

+

If you run more than one localized Docusaurus project on your computer, you should change the name of the environment variables to something unique (CROWDIN_PROJECTNAME_PROJECT_ID, CROWDIN_PROJECTNAME_API_KEY).

+

Since the files are generated, you do not need to have any files in your website/i18n or website/translated_docs directory as part of your repo. So you can can add website/i18n/* and website/translated_docs to your .gitignore file.

+
+

Automated File Sync Using CircleCI

+

You can automate pulling down and uploading translations for your files using the CircleCI web continuous integration service.

+

First, update the circle.yml file in your project directory to include steps to upload English files to be translated and download translated files using the Crowdin CLI. Here is an example circle.yml file:

+
machine:
+  node:
+    version: 6.10.3
+  npm:
+    version: 3.10.10
+
+test:
+  override:
+
+    - "true"
+
+deployment:
+  website:
+    branch: master
+    commands:
+      # configure git user
+
+      - git config --global user.email "test-site-bot@users.noreply.github.com"
+      - git config --global user.name "Website Deployment Script"
+      - echo "machine github.com login test-site-bot password $GITHUB_TOKEN" > ~/.netrc
+      # install Docusaurus and generate file of English strings
+      - cd website && npm install && npm run write-translations && cd ..
+      # crowdin install
+      - sudo apt-get install default-jre
+      - wget https://artifacts.crowdin.com/repo/deb/crowdin.deb -O crowdin.deb
+      - sudo dpkg -i crowdin.deb
+      # translations upload/download
+      - crowdin --config crowdin.yaml upload sources --auto-update -b master
+      - crowdin --config crowdin.yaml download -b master
+      # build and publish website
+      - cd website && GIT_USER=test-site-bot npm run publish-gh-pages
+
+

The crowdin command uses the crowdin.yaml file generated with the examples script. It should be placed in your project directory to configure how and what files are uploaded/downloaded.

+

Note that in the crowdin.yaml file, CROWDIN_PROJECT_ID and CROWDIN_API_KEY are environment variables set-up in Circle for your Crowdin project. They can be found in your Crowdin project settings.

+

Now, Circle will help you automatically get translations prior to building your website. The provided crowdin.yaml file will copy translated documents into website/translated_docs/, and translated versions of the i18n/en.json strings file will into i18n/${language}.json.

+

If you wish to use Crowdin on your machine locally, you can install the Crowdin CLI tool and run the same commands found in the circle.yaml file. The only difference is that you must set project_identifier and api_key values in the crowdin.yaml file since you will not have Circle environment variables set up.

+

Versioned Translations

+

If you wish to have translation and versioning for your documentation, add the following section to the end of your crowdin.yaml file:

+
  -
+    source: '/website/versioned_docs/**/*.md'
+    translation: '/website/translated_docs/%locale%/**/%original_file_name%'
+    languages_mapping: *anchor
+
+

Translated, versioned documents will be copied into website/translated_docs/${language}/${version}/.

+
← Navigation and SidebarsVersioning →
\ No newline at end of file diff --git a/docs/zh-CN/versioning.html b/docs/zh-CN/versioning.html new file mode 100644 index 0000000000..1b2a4e3022 --- /dev/null +++ b/docs/zh-CN/versioning.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/docs/zh-CN/versioning/index.html b/docs/zh-CN/versioning/index.html new file mode 100644 index 0000000000..1b2a4e3022 --- /dev/null +++ b/docs/zh-CN/versioning/index.html @@ -0,0 +1,120 @@ +Versioning · Docusaurus

1.3.1

Translate

Versioning

You can use the version script to cut a new documentation version based on the latest content in the docs directory. That specific set of documentation will then be preserved and accessible even as the documentation in the docs directory changes moving forward.

+

如何创建新版本

+

Run the following script to generate a starter versions page listing all the site versions:

+
yarn examples versions
+
+

This creates the pages/en/versions.js file.

+

You can edit this file later on to customize how you display the versions.

+

Add the following script to your package.json file if it doesn't already exist:

+
...
+"scripts": {
+  "version": "docusaurus-version"
+},
+...
+
+

Run the script with a command line argument of the version you wish to create. e.g.,

+
yarn run version 1.0.0
+
+

This will preserve all documents currently in the docs directory and make them available as documentation for version 1.0.0.

+

If, for example, you ran the version script with 1.0.0 as the version number, version 1.0.0 is considered the latest release version for your project. The site will display the version number next to the title in the header. This version number links to a versions page that you created earlier.

+

Documents in the docs directory will be considered part of version next and they are available, for example, at the URL docs/next/doc1.html. Documents from the latest version use the URL docs/doc1.html.

+

Running the script again with yarn run version 2.0.0 will create a version 2.0.0, making version 2.0.0 the most recent set of documentation. Documents from version 1.0.0 will use the URL docs/1.0.0/doc1.html while 2.0.0 will use docs/doc1.html.

+

This table below summarizes Docusaurus versioning at a glance:

+ + + + + + + + + + +
VersionTagURL
1.0.01.0.0docs/1.0.0/doc1.html
1.0.11.0.1docs/1.0.1/doc1.html
2.0.0currentdocs/doc1.html
master branchnextdocs/next/doc1.html
+

Versioning Patterns

+

You can create version numbers in whatever format you wish, and a new version can be created with any version number as long as it does not match an existing version. Version ordering is determined by the order in which versions are created, independently of how they are numbered.

+

Storing Files for Each Version

+

Versioned documents are placed into website/versioned_docs/version-${version}, where ${version} is the version number you supplied the version script.

+

The markdown header for each versioned doc is altered by renaming the id front matter field to original_id, then using "version-${version}-${original_id}" as the value for the actual id field.

+

Versioned sidebars are copied into website/versioned_sidebars and are named as version-${version}-sidebars.json.

+

A website/versions.json file is created the first time you cut a version and is used by Docusaurus to detect what versions exist. Each time a new version is added, it gets added to the versions.json file.

+

If you wish to change the documentation for a past version, you can access the files for that respective version.

+

Fallback Functionality

+

Only files in the docs directory and sidebar files that differ from those of the latest version will get copied each time a new version is specified. If there is no change across versions, Docusaurus will use the file from the latest version with that file.

+

For example, a document with the original id doc1 exists for the latest version, 1.0.0, and has the same content as the document with the id doc1 in the docs directory. When a new version 2.0.0 is created, the file for doc1 will not be copied into versioned_docs/version-2.0.0/. There will still be a page for docs/2.0.0/doc1.html, but it will use the file from version 1.0.0.

+

Renaming Existing Versions

+

To rename an existing version number to something else, first make sure the following script is in your package.json file:

+
...
+"scripts": {
+  "rename-version": "docusaurus-rename-version"
+},
+...
+
+

Run the script with command line arguments of first, the current version name, then second, the new version name. e.g.,

+
yarn run rename-version 1.0.0 1.0.1
+
+

Versioning and Translations

+

If you wish to use versioning and translations features, the crowdin.yaml file should be set up to upload and download versioned documents to and from Crowdin for translation. Translated, versioned files will go into the directory translated_docs/${language}/version-${version}/. For more information, check out the translations guide.

+
← Translations and LocalizationCLI Commands →
\ No newline at end of file diff --git a/es-ES/about-slash.html b/es-ES/about-slash.html index 8105c802c4..9afa774ef9 100644 --- a/es-ES/about-slash.html +++ b/es-ES/about-slash.html @@ -1,4 +1,4 @@ -About Slash · Docusaurus

1.3.1