New Crowdin updates

i18n/zh/docusaurus-plugin-content-docs/current/contribute/README.md

@@ -0,0 +1,50 @@
+# How to Contribute
+
+## Identify area for contribution
+
+There are several ways to identify the area where you can contribute to TON Docs:
+
+- Join [TON Docs Club chat](https://t.me/+c-0fVO4XHQsyOWM8) in Telegram and get the latest tasks from maintainers.
+- If you have a specific contribution in mind but are unsure about it, confirm whether
+  the contribution is appropriate by contacting one of the [Docs maintainers](/contribute/maintainers) directly.
+- Get familiar with the most frequently asked questions in the [TON Developers](https://t.me/tondev_eng) chats.
+- Please read over the [issues](https://github.com/ton-community/ton-docs/issues) in the GitHub repository.
+- Learn available [footsteps](https://github.com/ton-society/ton-footsteps/issues?q=documentation) for the documentation.
+
+## TL;DR
+
+- If you need to add or edit something in TON Docs, create a pull request
+  against the `main` branch.
+- The documentation team will review the pull request or reach out as needed.
+- Repository: https://github.com/ton-community/ton-docs
+
+## Development
+
+### Online one-click contribution setup
+
+You can use Gitpod (a free, online, VS code-like IDE) for contributing. It will launch a workspace with a single click and will automatically:
+
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/ton-community/ton-docs)
+
+### Code Conventions
+
+- **Most important**: look around. Match the overall style of the project. This includes formatting, naming files, naming objects in code, naming things in documentation, and so on.
+- **For documentation**: When editing documentation, do not wrap lines at 80 characters; instead, configure your editor to soft-wrap.
+
+Don't worry too much about styles in general; the maintainers will help you fix them as they review your code.
+
+### Pull Requests
+
+So you have decided to contribute code back to upstream by opening a pull request. You've put in a lot of effort, and we appreciate it. We will do our best to work with you and get the pull request reviewed.
+
+When submitting a pull request, please ensure the following:
+
+1. **Keep your pull request small**. Smaller pull requests (~300 lines of diff) are easier to review and more likely to get merged. Make sure the pull request does only one thing, otherwise please split it.
+2. **Use descriptive titles**. It is recommended to follow the commit message style.
+3. **Test your changes**. Describe your test plan in your pull request description.
+
+All pull requests should be opened against the `main` branch.
+
+## What Happens Next?
+
+The TON Docs team will be monitoring pull requests. Please help us by following the guidelines above to keep the pull requests consistent.

i18n/zh/docusaurus-plugin-content-docs/current/contribute/archive/hacktoberfest-2022/README.mdx

@@ -0,0 +1,51 @@
+import Button from '@site/src/components/button'
+
+# What is Hacktoberfest?
+
+<div style={{ textAlign: 'center', margin: '50px 0' }}>
+  <img alt="tlb structure"
+       src="/docs/img/docs/hacktoberfest.webp"
+       width="100%" />
+</div>
+
+[Hacktoberfest](https://hacktoberfest.digitalocean.com/) is a month-long celebration of _open-source projects_, their _maintainers_, and the entire community of _contributors_. Each October, open source maintainers give new contributors extra attention as they guide developers through their first pull requests.
+
+For the TON Community it's time to help ecosystem growth together, so let's join the whole world with our **Hack-TON-berfest** party and become _#1 open-source ecosystem of the year_!
+
+## How to Participate?
+
+The Hacktoberfest rules for 2022 are as follows:
+
+- **Hacktoberfest is open to everyone**!
+- Register anytime between September 26 and October 31
+- Pull requests can be made in any GITHUB or GITLAB project:
+  - [List of projects on TON Ecosystem](/hacktonberfest)
+  - [List of projects on GitHub](https://github.com/topics/hacktoberfest)
+- Have **4** pull/merge requests accepted between October 1 and October 31
+- The first 40,000 participants (maintainers and contributors) who complete Hacktoberfest can choose between two prizes: a tree planted in their honor or a Hacktoberfest 2022 t-shirt. _(from the Hacktoberfest community)_
+- Every participant (maintainer and contributor) to any of the TON Ecosystem projects will receive a [**Limited Hack-TON-berfest NFT**](#what-the-rewards). _(from TON Foundation)_
+
+For everyone in TON it's an opportunity to drive the growth of the entire ecosystem and receive cool rewards from TON Foundation. Let's do it together!
+
+## What are the rewards?
+
+To motivate the community to contribute to open source projects in the TON Ecosystem, you'll be able to receive a special reward from TON Foundation. Every participant will receive a **Limited Hack-TON-berfest NFT** achievement as a proof of participating:
+
+<div style={{width: '100%', textAlign:'center', margin: '0 auto'}}>
+  <video width="300" style={{width: '100%', borderRadius:'10pt', margin:'15pt auto'}} muted={true} autoPlay={true} loop={true}>
+    <source src="/docs/files/nft-sm.mp4" type="video/mp4" />
+        Your browser does not support the video tag.
+  </video>
+</div>
+
+:::info IMPORTANT!
+TON Foundation will mint a collection in November to all wallet addresses submitted to the [@toncontests_bot](https://t.me/toncontests_bot). It will happen after the calculation and validation of all contribution results.
+:::
+
+You have plenty of time to participate in the event. Let's build decentralized Internet of the future with thousands of contributors from all over the world!
+
+<Button href="/contribute/hacktoberfest/as-contributor"
+     colorType="primary" sizeType={'lg'}>
+    I want to become a Contributor
+  </Button>
+  <Button href="/contribute/hacktoberfest/as-maintainer" colorType={'secondary'} sizeType={'lg'}>I'm a Maintainer</Button>

i18n/zh/docusaurus-plugin-content-docs/current/contribute/archive/hacktoberfest-2022/as-contributor.md

@@ -0,0 +1,33 @@
+# Participate as a Contributor
+
+To become a contributor who receives a limited _Hack-TON-berfest NFT_, please set up your own [TON Wallet](https://ton.org/wallets) and verify your GitHub account.
+
+## Start your journey
+
+1. Set up any wallet from the [ton.org/wallets](https://ton.org/wallets) page. ([TON Wallet extension](https://chrome.google.com/webstore/detail/ton-wallet/nphplpgoakhhjchkkhmiggakijnkhfnd), for example.)
+2. Please provide your wallet address to the [@toncontests_bot](https://t.me/toncontests_bot) in Telegram.
+3. Validate your GitHub account in the same bot.
+
+After these steps you are ready to contribute and receive a [limited Hack-TON-berfest NFT](/contribute/hacktoberfest/#what-the-rewards).
+
+Welcome to the club, this is just the beginning!
+
+## New to contributing to open source?
+
+Hacktoberfest is a great place to start dipping your toes into open source contributions for the first time. There are plenty of streams, posts, guides, and discussions about to get started. You’ll be joining many folks who are also starting their journey this month!
+
+- [Basic information about Hacktoberfest for beginners](https://hacktoberfest.com/participation/#beginner-resources)
+- [Guide to making your first contribution](https://dev.to/codesandboxio/how-to-make-your-first-open-source-contribution-2oim) by Ceora Ford
+- [Practice the workflow to make your first contribution](https://github.com/firstcontributions/first-contributions)
+- [Overcoming imposter syndrome in open source contribution](https://blackgirlbytes.dev/conquering-the-fear-of-contributing-to-open-source)
+
+## How can I contribute to TON?
+
+The TON Ecosystem has several organizations and repositories:
+
+<span className="DocsMarkdown--button-group-content">
+  <a href="/hacktonberfest"
+     className="Button Button-is-docs-primary">
+    寻找贡献者的项目列表
+  </a>
+</span>

i18n/zh/docusaurus-plugin-content-docs/current/contribute/archive/hacktoberfest-2022/as-maintainer.md

@@ -0,0 +1,39 @@
+# Participate as a Maintainer
+
+The Hacktoberfest event is the best time of year to receive support from the community!
+
+If your repository is relevant to the TON Ecosystem, many contributors will be interested in it. Let's help them dive right into your project!
+
+## Prepare to party
+
+To handle contributors in the right way, you need to have a repository in good standing.
+
+Follow these best practices to prepare your project for contributions:
+
+1. Add the “hacktoberfest” topic to your repository to **OPT-IN TO HACKTOBERFEST** and indicate you are looking for contributions.
+2. Apply the “hacktoberfest” label to issues you want contributors to help you with in your GitHub or GitLab project.
+3. Please read and use [the essential tips for new open source maintainers](https://blog.ton.org/essential-tips-for-new-open-source-maintainers) by TON Society.
+4. Prepare to accept legitimate pull/merge requests by merging them, leaving an overall approving review, or adding the "hacktoberfest-accepted" label.
+5. Reject any spam requests you receive by labeling them as “spam,” and close or label any other invalid contributions as "invalid."
+
+Here is an example of a full repository: [ton-community/ton-compiler](https://github.com/ton-community/ton-compiler)
+
+After that, feel free to add your repository to the list.
+
+## Rewards for Maintainers
+
+As a repository maintainer in the TON Ecosystem, you will be able to receive two types of rewards:
+
+1. [Hacktoberfest Reward Kit](https://hacktoberfest.com/participation/#maintainers) (_see REWARD FOR MAINTAINERS_)
+2. [Limited Hack-TON-berfest NFT](/contribute/hacktoberfest/#what-the-rewards) (_please, register the wallet address in the [@toncontests_bot](https://t.me/toncontests_bot)_)
+
+## How to join and be listed?
+
+To participate in Hack-TON-berfest follow this link:
+
+<span className="DocsMarkdown--button-group-content">
+  <a href="https://airtable.com/shrgXIgZdBKKX64NL"
+     className="Button Button-is-docs-primary">
+    Add a repository to the list
+  </a>
+</span>

i18n/zh/docusaurus-plugin-content-docs/current/contribute/contribution-rules.md

@@ -0,0 +1,44 @@
+# Contribution Guidelines
+
+Before contributing any docs.ton.org page, please review the following list of general and important requirements to guarantee a smooth experience.
+
+## Naming
+
+- It is essential to ensure the correct use of _THE_ in the TON documentation. _TON Blockchain_ and _TON Ecosystem_ are capitalized terms, and therefore, do not require _THE_ in their usage.
+- We write _TON_ with regular nouns, and if it requires _THE_ according to English grammar, we use it. For instance: "_The_ TON Connect _protocol_ is a..."
+
+:::info
+TON Blockchain...
+
+TON Ecosystem...
+
+The TON Connect protocol...
+:::
+
+Please refer to the actual TON brand assets [here](https://ton.org/en/brand-assets).
+
+## Documentation References
+
+Every page in TON documentation should be finished with See Also section. Place there page, you think relates to current page without additional description.
+
+:::info
+
+```
+## See Also
+* [TON Contribution Guidelines](/contribute/contribution-rules)
+* [Tutorial Styling Guidelines](/contribute/tutorials/guidelines)
+```
+
+:::
+
+## English Helpful Sources
+
+The TON Ecosystem is being built for the entire world, so it's crucial that it's understandable for everyone on Earth. Here, we provide materials that are helpful for junior tech writers who want to improve their English skills.
+
+- [Plural Nouns](https://www.grammarly.com/blog/plural-nouns/)
+- [Articles: A versus An](https://owl.purdue.edu/owl/general_writing/grammar/articles_a_versus_an.html)
+
+## See Also
+
+- [TON Contribution Guidelines](/contribute/contribution-rules)
+- [Tutorial Styling Guidelines](/contribute/tutorials/guidelines)

i18n/zh/docusaurus-plugin-content-docs/current/contribute/docs/guidelines.md

@@ -0,0 +1,24 @@
+# Common Documentation Principals
+
+为了获得最佳的用户体验和清晰度，请在创建 docs.ton.org 上的新内容时，牢记我们旨在应用于所有文档的一般性和重要需求列表。
+
+## 为从业者制作的文档
+
+Documentations pages is primarily intended for documentation purposes and not as a tutorial, so it is important to minimize the use of personal examples or analogies in the text. It is crucial to ensure that the content is suitable for both professionals and non-professionals alike, while still providing valuable information.
+
+## Use a consistent format
+
+To make it easier for readers to navigate through the documentation, it is important to use a consistent format throughout the document. Use headings, subheadings, bullet points, and numbered lists to break up the text and make it easier to read.
+
+## Provide examples in special section
+
+Providing examples can help readers better understand the content and how to apply it. If you are writing documentation page and need refer several exmaples, please create special section Examples right before References and See Also sections. Do not mix description and examples in documentation pages.
+Use code snippets, screenshots, or diagrams to illustrate your points and make the documentation more engaging.
+
+## Keep it up to date
+
+Tech documentation can quickly become outdated due to changes in technology or software updates. It is important to review and update the documentation regularly to ensure that it remains accurate and relevant to the current version of the software.
+
+## Get feedback
+
+Before publishing the documentation, it is a good idea to get feedback from other contributors or users. This can help identify areas that may be confusing or unclear, and allow you to make improvements before the documentation is released.

i18n/zh/docusaurus-plugin-content-docs/current/contribute/docs/schemes-guidelines.mdx

@@ -0,0 +1,87 @@
+import ConceptImage from '@site/src/components/conceptImage';
+import ThemedImage from '@theme/ThemedImage';
+
+# Graphic Explanations Guidelines
+
+Maintaining consistency in documentation is crucial, and to achieve this, a specific standard for visualizing processes in smart contracts has been developed.
+
+## Graphic Explanation Notation
+
+### Message Processing Graph
+
+To depict message processing, it's advisable to utilize a graphical representation resembling a smart contract graph, complete with labels for transactions and messages.
+
+If the order of transactions doesn't matter, you can omit their labels. This simplifies the diagram, making it easier to read and understand the details related to messages and contracts.
+
+#### Annotation Primitives
+
+| Figure                                                                                                     | Description                                           |
+| ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
+| ![](/img/docs/scheme-templates/message-processing-graphs/circle_for_smart_contract.svg?raw=true)           | Circle - Smart Contract entity                        |
+| ![](/img/docs/scheme-templates/message-processing-graphs/rectangle_for_regular_message.svg?raw=true)       | Rectangle - Message Entity                            |
+| ![](/img/docs/scheme-templates/message-processing-graphs/dashed_rectgl_for_optional_message.svg?raw=true)  | Dashed Rectangle - Optional Message Entity            |
+| ![](/img/docs/scheme-templates/message-processing-graphs/line_for_transaction.svg?raw=true)                | Transactions (numeration optional) |
+| ![](/img/docs/scheme-templates/message-processing-graphs/person_figure_for_actor.svg?raw=true)             | Actor                                                 |
+
+- Avoid using big quantity different and bright colors.
+- Use the modification of figures, such as using a dashed border line.
+- For better comprehension, different transactions could be displayed with distinct line styles (solid and dashed).
+
+#### Message Processing Example
+
+<br></br>
+<ThemedImage
+  alt=""
+  sources={{
+    light: '/img/docs/message-delivery/message_delivery_2.svg?raw=true',
+    dark: '/img/docs/message-delivery/message_delivery_2.svg?raw=true',
+  }}
+/>
+<br></br>
+
+Learn references directly from Visio [message-processing.vsdx](/static/schemes-visio/message-processing.vsdx).
+
+### Formats and Colors
+
+#### Fonts
+
+- **Inter** fonts family  for all text within diagrams.
+
+#### Colors - Light Mode
+
+- Pencil Hand Drawn(default theme)
+
+#### Colors - Dark Mode
+
+- Font `#e3e3e3`
+- Background `#232328`
+- Light Highlight(arrows and scheme borders) `#058dd2`
+- Dark Highlight(arrows and scheme borders) `#0088cc`
+- InnerBackGround(for nested blocks) `#333337`
+
+#### Version Control Policy
+
+- Set diagrams in the documentation by SVG format for schemes to ensure readability on various devices.
+- Store original files in the project's Git repository under the "/static/visio" directory, making them easier to modify in the future.
+
+### Sequence Diagram
+
+In the case of complex and repetitive communication schemes between 2-3 actors, it is advisable to use a sequence diagram. For messages, use the notation of a common synchronous message arrow.
+
+#### Example
+
+<br></br>
+<div class="text--center">
+<ThemedImage
+  alt=""
+  sources={{
+    light: '/img/docs/message-delivery/message_delivery_7.svg?raw=true',
+    dark: '/img/docs/message-delivery/message_delivery_7.svg?raw=true',
+  }}
+/>
+</div>
+<br></br>
+
+### Scheme References
+
+- [message-processing.vsdx](/schemes-visio/message_processing.vsdx)

i18n/zh/docusaurus-plugin-content-docs/current/contribute/maintainers.md

@@ -0,0 +1,51 @@
+# Maintainers
+
+## Active Team
+
+Below is an alphabetical list of the current members on the TON Docs team.
+
+### Alex Golev
+
+TON Docs maintainer and DevRel at TON Foundation
+
+- Telegram: [@alexgton](https://t.me/alexgton)
+- GitHub: [Reveloper](https://github.com/Reveloper)
+
+### Gusarich
+
+Web3 Developer, [TON Dev community](https://github.com/ton-community) contributor, [TON Footsteps](https://github.com/ton-society/ton-footsteps) and TON Docs maintainer
+
+- Telegram: [@Gusarich](https://t.me/Gusarich)
+- GitHub: [Gusarich](https://github.com/Gusarich)
+
+### SwiftAdviser
+
+Developer Onboarding Manager at TON Foundation
+
+- Telegram: [@SwiftAdviser](https://t.me/SwiftAdviser)
+- GitHub: [SwiftAdviser](https://github.com/SwiftAdviser)
+
+## Acknowledgements
+
+TON Docs was originally created by [tolya-yanot](https://github.com/tolya-yanot) and [EmelyanenkoK](https://github.com/EmelyanenkoK).
+
+Over time, TON Docs has benefitted from the intellect and dedication of [numerous external contributors](https://github.com/ton-community/ton-docs/graphs/contributors). We extend our heartfelt gratitude to each of them.
+
+However, we would like to specially acknowledge the substantial contributions made by the following individuals. Their respective contributions have greatly enriched the quality and depth of our documentation:
+
+- [akifoq](https://github.com/akifoq): early contributions
+- [amnch1](https://github.com/amnch1): fixes
+- [aSpite](https://github.com/aSpite): content
+- [awesome-doge](https://github.com/awesome-doge): early contributions
+- [coalus](https://github.com/coalus): content
+- [delovoyhomie](https://github.com/delovoyhomie): content
+- [krau5](https://github.com/krau5): improvements
+- [LevZed](https://github.com/LevZed): content
+- [ProgramCrafter](https://github.com/ProgramCrafter): content
+- [siandreev](https://github.com/siandreev): content
+- [SpyCheese](https://github.com/SpyCheese): early contributions
+- [Tal Kol](https://github.com/talkol): early contributions
+- [TrueCarry](https://github.com/TrueCarry): content
+- [xssnick](https://github.com/xssnick): content
+
+Our sincere appreciation to each and every contributor who has aided in making TON Docs a rich and reliable resource.