docs(v2): releasing i18n blog post #4367
Conversation
slorber
added
the
pr: documentation
|
Deploy preview for docusaurus-2 ready! Built with commit 85157be |
|
[V1] Deploy preview success Built with commit 85157be |
|
Size Change: +31.5 kB (+6%) 🔍 Total Size: 564 kB
ℹ️ View Unchanged
|
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4367--docusaurus-2.netlify.app/classic/ |
| - **Scalable build-times**: allow building and deploying localized sites independently. | ||
| - **Localize assets**: an image of your site might contain text that should be translated. | ||
| - **No coupling**: not forced to use any SaaS, yet the integration is possible. | ||
| - **Easy to use with [Crowdin](https://crowdin.com/)**: multiple Docusaurus 1 sites use Crowdin, and should be able to migrate to v2. |
There was a problem hiding this comment.
You use the word "should" here. What would prevent a Docusaurus v1 site from not being able to migrate? Do we have a migration path / information for migrating? I think you can say something like:
multiple Docusaurus 1 sites use Crowdin, and we continue to support this valuable platform, including migration to v2.
There was a problem hiding this comment.
I still have to write this migration doc, it's in the top of my list.
I don't think we should say "docusaurus has first class support for crowdin". The 2 systems are 100% decoupled and we don't ship any code to add crowdin support, it just happens that both solutions are compatible.
Not sure it's a. good idea to commit to providing support in the place of the Crowdin support team
| - **Simple**: just put the translated files in the correct file-system location. | ||
| - **Flexible translation workflows**: based on Git (monorepo, forks, or submodules), SaaS software, FTP... | ||
| - **Flexible deployment options**: single, multiple domains, or hybrid. | ||
| - **Modular**: allow plugin authors to provide i18n support. |
There was a problem hiding this comment.
Do we have documentation about how to do this? Maybe link to it?
There was a problem hiding this comment.
this is also some api doc that is top priority for me to add.
| - **Low-overhead runtime**: documentation is mostly static and does not require a heavy JS library or polyfills. | ||
| - **Scalable build-times**: allow building and deploying localized sites independently. | ||
| - **Localize assets**: an image of your site might contain text that should be translated. | ||
| - **No coupling**: not forced to use any SaaS, yet the integration is possible. |
There was a problem hiding this comment.
Maybe give an example of a SaaS that you could integrate with in this bullet too.
There was a problem hiding this comment.
The next line mention Crowdin already, that does not seem too useful?
Maybe I should write "Easy to use with the Crowdin SaaS" instead to make it clearer Crowdin is such SaaS for which the integration is possible?
# Conflicts: # website/docs/i18n/i18n-introduction.md
Motivation
https://deploy-preview-4367--docusaurus-2.netlify.app/classic/blog/2021/03/09/releasing-docusaurus-i18n
(broken links are expected, they'll be fixed once all things are online)