Support i18n

[Kenzo-Wada]

Hi,

Are you considerring about supporting i18n?
if so, since Im a native Japanese speaker, I'd love to create Japanese document like ja.vike.dev at first if its ok.

Also, I thought that chinese site is old so that it should be archived or updated.

https://vike.dev/languages

[usk94]

@Kenzo-Wada
Hi, Kenzo! I'm Japanese as well, and if you don't mind, I'd like to do some documentation work with you too!😀

[usk94]

I recently started contributing to vike.js, and wanted to write a Japanese version of the documentation for the v1 design.
Sorry to interrupt, If you want to do it alone, feel free to let me know👌

[Kenzo-Wada]

Hi, @usk94 !

I'd appreciate if you'll work this with me! If core member of vike agree with this suggestion, lets do it together! 👌

[brillout]

A Japanese translation would be neat indeed 👍 I'd suggest the same we did for the Chinese translation, namely to copy the docs/ directory into in a new repository.

[Kenzo-Wada]

Thank you @brillout !

I've made repo for this project: https://github.com/Kenzo-Wada/vike-docs-ja
I'll let you know when it's all done and ready for deployed!

[Kenzo-Wada]

@usk94

I'll welcome your contribution. Be free for asking me help if anything!
(Also, lets speek in japanese if you dont mind. it's more smooth for me lol)

[usk94]

@Kenzo-Wada

Thanks for creating the repository!😆
Ok, let's communicate in Japanese during the documentation process.
(たのしみです、よろしくお願いします😆)

[Kenzo-Wada]

@brillout

As we both discussed efficient ways to sync changes to the vike.dev docs, we came to the conclusion that it would be better to create a folked repository instead of creating a new repository. What do you think?

The reason is that if we start with a completely separate repository, we would have to manually catch and fix changes to the vike.dev docs, which would take a lot of man-hours and would likely result in leaks.
On the other hand, I'm concerned that if we folk, we'll be importing the contents of directories other than docs that we don't need.