feat(i18n): support translating through locale extensions myDoc.fr.md
#9700
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Translating through the
i18n
folder is nice for i18n SaaS integrations (Crowdin)But it is not ideal for simpler needs based on Git, as it requires to explain the i18n folder structure convention.
To make i18n simpler to adopt, let's add support for localized file extensions to all our core content plugins
./docs/myDoc.fr.md
./blog/myBlog.fr.md
./src/pages/myPage.fr.tsx
This kind of convention is already used by other documentation frameworks:
Note, we also want to support this for metadata files:
_category_.fr.yml
authors.fr.yml
Note, the
editUrl
andeditLocalizedFiles
options should rather work as expected tooTest Plan
Unit tests + dogfood
Test links
https://deploy-preview-9700--docusaurus-2.netlify.app/
Local: