chore(i18n,docs): processed translations (#45452)

docs/i18n/chinese-traditional/_sidebar.md

@@ -21,6 +21,7 @@
   - [Understand the curriculum file structure](curriculum-file-structure.md)
   - [Debug outgoing emails locally](how-to-catch-outgoing-emails-locally.md)
   - [Set up freeCodeCamp on Windows (WSL)](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/chinese-traditional/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.

docs/i18n/chinese/_sidebar.md

@@ -21,6 +21,7 @@
   - [Understand the curriculum file structure](curriculum-file-structure.md)
   - [Debug outgoing emails locally](how-to-catch-outgoing-emails-locally.md)
   - [Set up freeCodeCamp on Windows (WSL)](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/chinese/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.

docs/i18n/espanol/_sidebar.md

@@ -21,6 +21,7 @@
   - [Entiende la estructura de archivo del currículo](curriculum-file-structure.md)
   - [Depurar correos salientes localmente ](how-to-catch-outgoing-emails-locally.md)
   - [Configura freeCodeCamp en Windows (WSL)](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/espanol/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.

docs/i18n/german/_sidebar.md

@@ -21,6 +21,7 @@
   - [Verstehe die Dateistruktur des Studienplans](curriculum-file-structure.md)
   - [Ausgehende Emails lokal debuggen](how-to-catch-outgoing-emails-locally.md)
   - [freeCodeCamp auf Windows einrichten (WSL)](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/german/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.

docs/i18n/italian/_sidebar.md

@@ -21,6 +21,7 @@
   - [Capire la struttura dei file del curriculum](curriculum-file-structure.md)
   - [Fai il debug delle email in uscita localmente](how-to-catch-outgoing-emails-locally.md)
   - [Settare freeCodeCamp su Windows (WSL)](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/italian/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.

docs/i18n/japanese/_sidebar.md

@@ -21,6 +21,7 @@
   - [カリキュラムのファイル構造を理解する](curriculum-file-structure.md)
   - [送信メールをローカルでデバッグする](how-to-catch-outgoing-emails-locally.md)
   - [freeCodeCamp を Windows (WSL) でセットアップする](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/japanese/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.

docs/i18n/portuguese/_sidebar.md

@@ -21,6 +21,7 @@
   - [Compreender a estrutura do arquivo do currículo](curriculum-file-structure.md)
   - [Depurar e-mails enviados localmente](how-to-catch-outgoing-emails-locally.md)
   - [Configurar freeCodeCamp no Windows (WSL)](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/portuguese/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.

docs/i18n/ukrainian/_sidebar.md

@@ -21,6 +21,7 @@
   - [Ознайомлення зі структурою файлів навчальної програми](curriculum-file-structure.md)
   - [Налагоджуйте вихідні електронні листи локально](how-to-catch-outgoing-emails-locally.md)
   - [Встановіть freeCodeCamp на Windows (WSL)](how-to-setup-wsl.md)
+  - [User Token Workflow](user-token-workflow.md)
 
 ---
 

docs/i18n/ukrainian/user-token-workflow.md

@@ -0,0 +1,15 @@
+# How the User Token Workflow Works
+
+User tokens are used to identify users to third parties so challenges completed using those services can be saved to a user's account.
+
+## How they are created
+
+At the moment, the tokens are only used to submit the Relational Database challenges. A token gets created when a signed in user clicks the "Click here to start the course" or "Click here to start the project" buttons to start one of the Relational Database courses or projects.
+
+## When they get deleted
+
+A user token will be deleted when a user signs out of freeCodeCamp, resets their progress, deletes their account, or manually deletes the token using the widget on the settings page.
+
+## How they work
+
+Tokens are stored in a `UserToken` collection in the database. Each record has a unique `_id`, which is the token, and a `user_id` that links to the user's account from the `user` collection. The token is encoded using JWT and sent to the client when it's created. That encoded token is then given to third party services that need it and sent to our API by them when a challenge is completed. When our API gets it, it is decoded so we can identify the user submitting a challenge and save the completed challenge to their `completedChallenges`.