Open gaearon opened 1 year ago
Hi all, I will pick useCallback
hook page
Hi all, I will translate Tutorial: Tic-Tac-Toe
page
https://vi.react.dev/learn/tutorial-tic-tac-toe
I've added a draft PR: https://github.com/reactjs/vi.react.dev/pull/346
Hi all, I will pick the Installation
index page
https://react.dev/learn/installation
Hi guys, I will pick the Thinking in React
page
https://vi.react.dev/learn/thinking-in-react
@nampdn @ltmylinh @cuongtran8 @Ryan-LT
Can you please confirm whether you'd be able to steer and maintain this translation? We'd like to get https://github.com/reactjs/translations.react.dev/blob/main/langs/vi.json updated to list active maintainers. Thank you!
@nampdn @ltmylinh @cuongtran8 @Ryan-LT
Can you please confirm whether you'd be able to steer and maintain this translation? We'd like to get https://github.com/reactjs/translations.react.dev/blob/main/langs/vi.json updated to list active maintainers. Thank you!
Hi @gaearon, yes I will be able to do it.
@gaearon I can help with that.
Hi guys, I will pick the Writing Markup with JSX
page.
https://react.dev/learn/writing-markup-with-jsx
@nampdn @ltmylinh @cuongtran8 @Ryan-LT
Can you please confirm whether you'd be able to steer and maintain this translation? We'd like to get https://github.com/reactjs/translations.react.dev/blob/main/langs/vi.json updated to list active maintainers. Thank you!
Hi @gaearon , There are some texts that are being rendered in English from the React components.
So Should we translate these texts in the component itself - I mean we modify these texts in components directly?
or Should we leave it as English on our website?
or Should we modify these components so we can pass these texts as props?
Do you have any thoughts on this? Thanks.
Hi all, I would like to pick the useDebugValue
page
Hi all, I would like to pick the State as a Snapshot page
@ltmylinh
Should we translate these texts in the component itself - I mean we modify these texts in components directly?
I think it's up to individual translations to decide. I'm not sure. I could see it going either way — I suggest to decide this with other translation maintainers.
Hi all, I have several pull requests waiting to be reviewed and merged. Could the maintainers please help me out by reviewing them? My PRs include:
Beside, I want to pick the "Fragment" page: https://vi.react.dev/reference/react/Fragment and the Profiler page Thanks in advance
I will translate the Your First Component
page https://react.dev/learn/your-first-component
Hi guys, I would like to translate useState
page: https://react.dev/reference/react/useState
Hi all, I would like to pick the Render and Commit
page.
https://react.dev/learn/render-and-commit
Hi @gaearon, I think you should update the glossary link to https://github.com/reactjs/vi.react.dev/issues/2 instead of this issue's url.
Before contributing, read the glossary and style guide to understand how to translate various technical and React-specific terms.
Hi all, I would like to translate Responding to Events
page.
https://react.dev/learn/responding-to-events
Hi @gaearon, I think you should update the glossary link to #2 instead of this issue's url.
Before contributing, read the glossary and style guide to understand how to translate various technical and React-specific terms.
updated. Thanks.
Hi, I will translate the lazy
page: https://vi.react.dev/reference/react/lazy
Thanks
Hi, I will translate the StrictMode
page: https://vi.react.dev/reference/react/StrictMode
Thanks
Hi guys i will translate the Reacting to Input with State page
Hi all, I would like to pick the Rendering Lists
page.
https://react.dev/learn/rendering-lists
Hi, I'm translating State: A Component's Memory
page next.
https://react.dev/learn/state-a-components-memory
Hi all, I would like to translate the <Suspense>
page next.
https://vi.react.dev/reference/react/Suspense
Hi there, I'd like to take the useEffect
api reference, or anything that I can help with, Code Review maybe. cc @gaearon
Hi all, I would like to translate useSyncExternalStore
page.
Hi there, I'd like to take the react-dom/server
, cc @gaearon
Hi there, I would like to translate the learn/updating-objects-in-state
page if it's available. Thank you!
Hi there, I would like to translate the learn/updating-arrays-in-state
page. Thank you!
Maintainers
For New Translators
To translate a page:
Before contributing, read the glossary and style guide to understand how to translate various technical and React-specific terms.
You can use the Crowdin as a base for your translation. Make sure to compare the content with the current React website to make sure everything is up to date! (NOTE: delete this if the language doesn't have any Crowdin contributions)
Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.
For maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
Main Content
To do before releasing as an "official" translation. Please translate these pages first.
Note that each section has an index page, which needs to be translated too.
Learn React
[ ] Quick Start (@ltmylinh) #415
[x] Installation (@ninh-nd) #347
[ ] Describing the UI
[ ] Adding Interactivity
[ ] Managing State
[ ] Escape Hatches
API Reference
[ ]
react
: HooksuseCallback
(@Quynh-Nguyen)useContext
useDebugValue
(@viettrung9012) #364useDeferredValue
useEffect
useId
useImperativeHandle
useInsertionEffect
useLayoutEffect
useMemo
useReducer
useRef
useState
(@nguyentran-se)useSyncExternalStore
(@hoangtrung99) #413useTransition
[ ]
react
: Components<Fragment> (<>)
(@leduc1901) #352<Profiler>
(@leduc1901) #355<StrictMode>
(@leduc1901)<Suspense>
[ ]
react
: APIscreateContext
forwardRef
lazy
(@leduc1901) #361memo
startTransition
[ ]
react-dom
: Components<div>
)<input>
<option>
<progress>
<select>
<textarea>
[ ]
react-dom
: APIscreatePortal
flushSync
findDOMNode
hydrate
render
unmountComponentAtNode
[ ]
react-dom/client
: Client APIscreateRoot
hydrateRoot
[ ]
react-dom/server
: Server APIsrenderToNodeStream
renderToPipeableStream
renderToReadableStream
renderToStaticMarkup
renderToStaticNodeStream
renderToString
Navigation and UI
We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.
HomeContent.js
)src/sidebar*.json
)TopNav.tsx
)When You're Ready...
After everything above is translated, add your language to
deployedLanguages
inSeo.tsx
of the original reactjs/react.dev repository.Secondary Content
These API pages should ideally be translated too, but they're less urgent and can be done after the others:
Children
cloneElement
Component
createElement
createFactory
createRef
isValidElement
PureComponent
Optional Content
These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages: