[docs/french] Translate official document to French

[fguitton]

• docs
  • Introduction
    • Motivation
    • Core Concepts
    • Installation
    • Getting Started
  • Basic Tutorial
    • Intro
    • Atoms
    • Selectors
    • Bonus: Performance (Didn't release)
  • Guides
    • Asynchronous Data Queries
    • State Persistence
  • API Reference
    • Core
      • atom()
      • selector()
      • isRecoilValue()
    • Hooks
      • useRecoilState()
      • useRecoilValue()
      • useSetRecoilState()()
      • useResetRecoilState()()
      • useRecoilValueLoadable()()
      • useRecoilStateLoadable()()
      • useRecoilCallback()()
    • Utils
      • atomFamily()
      • selectorFamily()
      • constSelector()
      • errorSelector()
      • noWait()
      • waitForAll()
      • waitForAny()
      • waitForNone()

[drarmstr]

@fguitton - This PR is currently a "draft," what's your plan for wanting to merge?

[fguitton]

@drarmstr I'm going to proceed with translating what's left to translate in the coming few days, once that's done I'll be marking this ready for review.

[fguitton]

@drarmstr I believe I have completed the first treatment of the documentation including the latest changes from the docs branch. There might be the need to pass over this again with a refreshed eye but all of the topics have been translated to french.

[drarmstr]

@fguitton - To merge these translations and actually get them published seems like we need to add links to the translations somewhere. @Mark-Yoo was looking at that for the Korean translations in #892, but I'm not sure if he came to a solution yet if you'd like to help?

[fguitton]

@drarmstr, @Mark-Yoo, I have worked in the last commit (31076a5) on making things compile with the french Markdown.
You will see that running docusaurus build now builds for both language and produces a build folder containing everything (See below).

I realise now that the other pages will probably have to be dealt with differently, probably relying on the <Translate /> component and the JSON language files.

What are your thoughts ?

[drarmstr]

@fguitton - Oh, this looks promising! looks like a single yarn build will build for all languages. Can you clarify if this solves how the end user would access the translations?

[fguitton]

@drarmstr That's correct, everything gets built with a single yarn build command. I then served everything with serve .\build\ to test everything worked appropriately. Although, in development mode (when using yarn start) one must apparently select which locale they want Docusaurus to serve, like so: yarn start -- --locale fr (Defaults to existing en otherwise).

Regarding what it will be for users, I am directly making use of the built-in locale selector :
There is a couple of different positions to chose from, I found https://reactjs.org and https://docusaurus.io had their own locale menu in the top right so I went for the same.

Recoil/docs/docusaurus.config.js

Lines 69 to 72 in 3a76d01

	{
	type: 'localeDropdown',
	position: 'right',
	}

And this yields the following screen:

(I also noticed the latter had historical version documentation as well, something Recoil could leverage later ?)

[drarmstr]

Excellent @fguitton, this looks exactly like what we need! I'm catching up now after getting back to work. Is everything here look good for merging the PR now? Could we then merge #892 right after this?

[Mark-Yoo]

@drarmstr All Korean translations are merged into #18 instead of #892. so you can merge #18, not #892.
#892 will be closed after the #18 is merged :)

[drarmstr]

@drarmstr All Korean translations are merged into #18 instead of #892. so you can merge #18, not #892.
#892 will be closed after the #18 is merged :)

Great, thanks! Ok, then I'll merge this and then #18 after getting the go-ahead from @fguitton .

[alstn2468]

@fguitton How can we pass translation data in the index.js and resources.js in the pages folder?

[fguitton]

@drarmstr, Yes, this is fully ready now It's a green light for me. I took the liberty to add the extra commit to translate the home (index.js) and resources (resources.js) pages as well. Giving us something like below. @alstn2468, you can see how I've gotten that done via the <Translate /> API on commit ee54104

[drarmstr]

@fguitton - The French translation is now live! Merci!