 because of my poor English, so I will finish my share in Chinese later. But my PowerPoint, I use Chinese and English both. And actually there is a transaction link. I send the link to the chat. Okay, I will begin my presentation. Hello, everyone. I am very happy to have this opportunity today, and to have a talk with you on the global market. I would like to share with you some of the experience of the project. And some of the work I have done before. Let me introduce myself. I currently work at the Institute of Information Research in China. I am a blockchain engineer. And at the same time, I am also the head of the China Technology Working Group of the Superfunds. I am mainly in charge of the cultural internationalization and education of this project. At the same time, I will organize some super funds for some activities in China. Okay, today I will share with you the theme of documents as important as codes. It is the same importance of Wendang and the code. I think the name is a bit vulgar, simple and simple. But to talk about this, there should be a lot of developers who will often ignore something when they maintain a project. As a developer coder, when we write code, the most important thing is to write a good code, to seal up a method, and to design a project. But we will often ignore the process of users using it. The first thing they see is documents. It is Wendang. When a user is not familiar with this project, he must first look at our Wendang. At this time, our official Wendang or the Rhythmie project will be a very, very important entrance. In the process of participating in the Superfunds' community activities, I have also participated in the translation of the February official Wendang. Now, the Chinese version of Fabric Wendang has completed 1.4.2 and 2.2.2.2.2.2.2.0. Of course, the Wendang of 2.2.0 should have a small part of it. I haven't translated it yet, but I have completed most of it. Okay, let's go into my first page. Here, I would like to share with you why I still think that Wendang is a project. Why should we do it? Like what I just said, first of all, Wendang is the first material to learn a project. The documents are the first-time materials when starting linear project. Most of the users will use it like this. Especially when I first started to work with Fabric, I was actually looking at the official Wendang. My English reading ability is okay. So, I've been studying English Wendang for a very difficult time. I started to learn a little bit. I learned how to build a test network, and how to build a chain. I also learned how to develop the application. Of course, Wendang has provided a lot of help to my input. Also, Wendang has improved the 1.0.2.2.0. Documents make it easier to use and more friendly. This is what I just said. After we have such a Wendang, everyone can quickly get started with this project. Only then can you quickly use this project to develop Wendang. And then you have a lot to do. For example, you need to read the source code, and then you can find some problems and know how to use them. At the same time, Wendang is relatively better than the video when we are familiar with a project. Because Wendang, you can read it repeatedly, and then find out the meaning of each sentence. But when you listen to the video, you might want to re-hear the content after listening to it for a while. It's not that convenient. It's not as convenient as Wendang. It's so friendly. Another very, very important point is that Wendang's internationalization is very important. It helps to promote the project. The international documents promote the project globalization. We have a lot of open source projects now. Wendang is mainly English. There may be many reasons. One of them may be because the developer of the project is originally a person who speaks English. At this time, he uses English to write this document. Another one is in the Chinese community. In fact, a very common problem in Chinese companies and open source communities is that after the development of our Chinese project, in order to promote globalization, it is convenient to use non-English as the country's developer. We will also write a English document. This Wendang is very, very good for the project promotion. So Wendang's internationalization is also a point that we need to pay attention to in the development process of the project. Okay. Next, I will use my most familiar hyperliger as an example. Then I will talk about this document. Wendang is in Wendang. What kind of work should Wendang do? First of all, Fabric is currently the most popular project. It is under the super-brand project. Fabric should be the most popular project. Its document is also very, very long. At the same time, of course, it is also very good. Currently, Fabric's document should have about 16 chapters. I have summarized a little bit about its number. It is English version. It should be about 18 million words. There are plenty of pictures in the middle. And then the flow picture, the Yongdao picture, etc. It is very, very clear to describe the word. Fabric's Wendang has always been my favorite project Wendang. In Wendang, it also includes application experience. For example, Paper Knight. He is in the process of using Fabric. Then how to develop a project, and then think about it with which way to think. There is a relatively good experience. In addition, his drawing is very rich. At the same time, his drawing is also beautiful compared to his drawing. So I think Fabric Wendang should be one of the most popular projects. It is a model that is worth learning. At the same time, of course, there is actually a Wendang working group in Hyperlegia. Fabric's Wendang actually has a lot of members of the working group. And then it's hard to write. And then after a lot of discussion, a lot of comments, Then it was presented such a more rich, more beautiful Wendang. And then there is the work of internationalization. Actually, Hyperlegia is also actively promoting the internationalization of Fabric Wendang. At present, I have summarized it a little. Now, in official Wendang, there is already a ten language translation. These language translation work progress may be some parts of the language are not particularly fast. But we are slowly starting to contribute. Because in 2017, Chinese society began to organize everyone to translate Chinese. To translate Fabric Wendang into Chinese. So for now, Chinese Wendang translation progress will be faster. At the same time, we have actually already completed In Fabric official Wendang, read the docs, When you click on the right corner of the website, ZHCN and then release 1.4 In fact, this version of the Wendang is translated into 1.4.2. 1.4.2 Wendang translation is actually a very, very huge amount of work. Because in the process of translation, the speed of the update of Fabric Wendang is very fast. But because we are supporters of translation, we are not full-fledged. So the progress of translation will be slower. After that, Fabric Wendang has been updated again. So we have to be very busy again. Then save the script and update the new version of the new version. So there is no complete version of the Wendang translation until 1.4.2. At that time, I felt that this Wendang has been translated for a very long time. We have to have a period of success. So with the friends of the organization community, Then translate Wendang in a few sentences and then translate it out. After 1.4.2 translation, In fact, on the official Twitter of HappyLegend, Then it was also published. I think it's still a very happy thing. After Fabric 2.0 came out, We started to translate from 2.2.0. Currently, the Wendang of 2.2.0 has been translated most of the time. And a small part of Zhang Jie, There may be some places that need to be reimbursed to complete it. In translation work, In fact, it's not just about HappyLegend. My current work unit is the Chinese Information Research Institute, CAICT. In fact, we are also particularly important in Wendang's international work. We actually made a few research reports here. It's called the industrial blockchain application guide. This guide, our first version is actually written in Chinese. After we wrote it, It's also connected to the HappyLegend community. Then in the community, I just sent a notice to see if anyone is willing to share this content. Then there are also some people helping the community here. Then translate this Chinese research report into English. And now it has been launched in the Kaxing district of Wendang. Then TWGC, Our TWGC is actually a technical work group in China. It's a super-priced Chinese technical work group. Our work group is now... In fact, our volunteers started in 2017 In the Wendang of 2.2.0. In addition to the official Wendang of Fabric, In fact, we also translated the HappyLegend Cactus project. Then there is the HappyLegend推文. And some of the HappyLegend bloggers. We will do some translation. And now we are also doing some translation work And then we are making a video tutorial of Fabric's Chinese. Now we are not in Bilibili. There is also a video in Tengxun. I will share the Wendang of Fabric with you. And then we will share it with you. In the process of translating Wendang for a project, we should use the process to make a contribution. Of course, we can't say that the process is a perfect process. But first of all, its advantage is that the usage threshold is relatively low. The friends who write code are actually more familiar with the way of using Git. It is relatively convenient to use. The other one is that the tools for the outside are relatively less rely on. So we will reduce the complexity of everyone's contribution. First of all, when we translate Fabric's Wendang, we should also focus on the Wendang warehouse of HappyLegend Fabric. This is the location of the Wendang warehouse. For those who usually use Git less, they may need to install a Git first. Git is a tool that controls the code version. Here we also use it to do Wendang management. And then you have to set up SSH in your Git Hub account. After that, you can use Git cloning. And then check out the part you want to translate. For example, what we want to translate now is the part of Release 2.2. Then we will check out Gumbi and then Release 2.2. And then we can translate it. This is the preparation work of the previous period. And then the second step needs to take a task. Because our Wendang translation and code development are actually very similar. There are a lot of people who coordinate the process. So in order to make it easier for everyone to coordinate, in order to let everyone do less repetitive work with a Wendang. So we opened E-shape on GitHub. Every E-shape is actually an upper translation article. In this way, if you want to translate one of the articles, you can leave a message below the E-shape. And then the manager will see your message and give you this E-shape. At this time, everyone knows that this task has been approved. There will be no repeaters to do this work. After that, you can translate it. Here I will make up for it. In the process of translation, in fact, we usually use our own more common tools, such as VS Code, IDEA, or Atom, Tepadro, etc. You can translate it in your own way. After the translation is complete, the article needs to be uploaded. When it is uploaded, we still need to maintain the original format of the original document. For example, the original format is Macdown or RST format. We still need to submit it according to the original document. When it is uploaded, first of all, it needs to be sent off like the other rules in HyperLager. In Commuter, add an S parameter. Then submit it to your own Folk warehouse. Then in the warehouse, the new PR, like the original HyperLager Fabric Docs 18N, in this warehouse, apply the content that you have translated to the official warehouse. Then you can wait for the review of the director and the relevant correspondence. If the director has a comment on what you have translated, he will leave some comments. Then you can follow the director's comments and process your translation. After the process is complete, the director will send it to the official warehouse. Then you can see your shared document in the RST Docs page. It is shared with Fabric as an example to share how to contribute to an original project. That is, the process of contribution. Then below is my summary of a good original project document. What kind of content should be there? First of all, I think a good document must have a clear draft. This draft is a general idea in the process of learning this document. For example, the right side is Fabric's draft. The right side is a draft of Fabric's document. In my summary of the process, I actually took a lot of reference to Fabric's draft. Of course, Fabric's document is a bit different from the actual content of his document after a lot of rounds of waiting. But his draft is still okay. I think that there must be a project introduction first. With the project introduction, everyone can know this project, understand the work of this project, and then decide whether to continue to use and learn this project. The second step is the environment. Because of the software environment, each part of the software may have different development languages and development environments. So there needs to be an environment to tell the developer how to prepare a suitable environment for their later use. The third step is the speed input. The speed input is to guide the developer to use the speed input and then use the speed input to use the speed input in the project. In the speed input, we can write a sample or a test for the project. Everyone can quickly pass this sample and know what the project is running. At the same time, in the process of learning, you can also pass this sample and analyze the source code. It is convenient for you to do some application development. The key concept is that when there is a general understanding of a project, we need to explain to the users what our project is. Because in different projects, it may have some different concepts and key words. For example, in Fabric, its channel, its MSP, these concepts are not used by other developers of Fabric. They may not understand and accept everything at once. So here we still have to introduce some of the key concepts in our project. There is also a key function. After we have the concept, we need to introduce the functions of our project. What can our project do? For example, in Fabric, we need to support some data sources, we need to support some public calculations, and then how to use the test, how to develop the code. This function should be introduced in the key function, mainly to the developers to introduce my project. What can we do? And then the introduction of the high-end such as the design of the system architecture. For a person who is familiar with how to use the project, the application is just in the surface of the project. Later, if you want to have a deeper understanding and a deeper application of this project, you still can't know the architecture of the system. So here it's best to write a description about the architecture design and tell the user, the developer, what is our system thinking about from the beginning and how to do it. In the middle, how to design some models. And then whether it is the design of a cross-dialogue, a cross-dialogue design. And then how to support the data source, these may be needed in the architecture design and then to explain to the user. Of course, the architecture design is the best. In fact, I especially like to show you the picture drawn by Zhang Jie, the process of transaction in Firebreak. The process of transaction is a very core process in a blockchain system. As long as you understand the process of transaction of a blockchain system, you will understand much more. This is in the architecture design of Firebreak. Since the project is open, I would like to let you participate in the project and learn and discuss together. Therefore, we need to write a reference paper to tell the developer how to participate in our project. Of course, I think the reference paper can be divided into two parts. The first one is how to contribute to our project document or how to do some contributions for our project plan or translation work. There is also the reference paper written by Bo Ke for example. There is also a common question. In fact, in the process of using a new project, we often encounter a lot of problems. However, for some experienced developers, these problems can be solved. Therefore, we can put the common question in FAQ and tell you how to solve the problem. In addition to the documents, we also have a good document written by Bo Ke. Although the document can't be as detailed as writing a poem, but a good document can be better written. The language needs to be simplified and clearer. For people who read the document, it may be easier to understand it. In addition, there needs to be a beautiful painting. The description of the pure text is actually compared to the painting, the understanding will be a little slower. If you match a beautiful painting, for example, a poem painting, a process painting or a structure painting, then in the process of understanding the whole article, there will be a great sense of intuition through these paintings. Then, with the following文字解释, you can quickly understand what the painting needs to be described. The right side is the painting that I took out from the official document of FAQ. I think these paintings are very helpful to me in the whole FAQ process. When I can't see it, I take a picture of each painting and explain it to understand the function of FAQ. So, a beautiful painting is still very important for the whole document. However, our developers pay attention to the code on the code every day. So, we have more code. When we write a document, we want to stick the code directly to it. For example, we define a block structure. I want to tell others in the article what my block structure looks like. At this time, a developer may directly stick the definition of the word in Pro Auto. However, this method is not very good. Compared to this method, the better way is to draw a picture to understand the meaning of each block. In this way, people will understand more easily. Then, there are some problems in making a document. First of all, the issue of the contribution of the document. Many developers don't like to write a document because they pay more attention to the beauty of the code because many developers only pay attention to the contribution of the code. So, they ignore the contribution of the project document. This is the issue of the contribution of the document. And the issue of the contribution of the document. In fact, there are many versions of the code such as IDE and so on. But for the contribution of the document, there is not a very good contribution platform. Especially, this part of the translation is not very good. It uses a very comfortable translation tool. So, the contribution of the document is still lacking. There is also a question of the standard of the document. There is no standard of the standard of the document. So, when everyone writes a document, most of them are based on some experience and some of them are based on their own rules. So, writing a document may have some disadvantages. And the third one is the question of language. In order to promote the project, many projects will write English documents. But in fact, there are many people who do not speak English. So, we may need to do some local work and then do some translation work to translate the document into the language of our own country. And then we can use the language of our own country to help other people use their own projects. OK. This is the main content I shared today. And then there is still a little time to see if you have any questions to discuss. OK. So, this is the sharing of today. Thank you everyone.