[lexical-website] Feature: Traditional Chinese Localization

[Edit-Mr]

Description

Add Traditional Chinese Localization for docs

Here's an demo I deployed: https://lexical-lexical-website-git-demo-editmrs-projects.vercel.app/zh-Hant/

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
lexical	❌ Failed (Inspect)			Aug 29, 2024 3:50pm
lexical-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 29, 2024 3:50pm

[facebook-github-bot]

Hi @Edit-Mr!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[github-actions]

size-limit report 📦

Path	Size
lexical - cjs	29.38 KB (0%)
lexical - esm	29.22 KB (0%)
@lexical/rich-text - cjs	37.87 KB (0%)
@lexical/rich-text - esm	31.08 KB (0%)
@lexical/plain-text - cjs	36.45 KB (0%)
@lexical/plain-text - esm	28.44 KB (0%)
@lexical/react - cjs	39.64 KB (0%)
@lexical/react - esm	32.52 KB (0%)

[ivailop7]

Hi there, the deployment still fails. Also, I'm unsure how the maintenance is going to be done of this documentation going forward and keep it in sync with the english language one.

[etrepum]

I agree with @ivailop7, this would be very difficult for the existing team to maintain. Maybe it would be better to maintain this externally, and when Lexical is more stable (>1.0 for sure) and has a larger team then official translations could be reconsidered, possibly following the translations.react.dev model