3pp-mirror/docusaurus
1
0
Fork 0
mirror of https://github.com/facebook/docusaurus.git synced 2025-08-04 09:19:16 +02:00
Code Issues Projects Releases Packages Wiki Activity

fix(cli): allow passing a list of file names to write-heading-ids (#6500)

Browse source
This commit is contained in:
Joshua Chen 2022-01-29 12:21:15 +08:00 • committed by GitHub
parent 9af7aae9e2
commit c1e3801ee7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
28 changed files with 74 additions and 74 deletions
Download patch file Download diff file Expand all files Collapse all files

6
website/docs/i18n/i18n-tutorial.md
View file

@ -102,7 +102,7 @@ After copying files around, restart your site with `npm run start -- --locale fr
:::
### Translate your React code
### Translate your React code {#translate-your-react-code}
For any React code you've written yourself: React pages, React components, etc., you will use the [**translation APIs**](../docusaurus-core.md#translate).
@ -258,7 +258,7 @@ You can see the calls to the translation APIs as purely _markers_ that tell Docu
:::
### Translate plugin data
### Translate plugin data {#translate-plugin-data}
JSON translation files are used for everything that is interspersed in your code:
@ -450,7 +450,7 @@ It is also possible to deploy each locale as a separate subdomain, assemble the
- Deploy your site as `fr.docusaurus.io`
- Configure a CDN to serve it from `docusaurus.io/fr`
## Managing translations
## Managing translations {#managing-translations}
Docusaurus doesn't care about how you manage your translations: all it needs is that all translation files (JSON, Markdown, or other data files) are available in the file system during building. However, as site creators, you would need to consider how translations are managed so your translation contributors could collaborate well.