Everyone in remote office works together to realize cooperative editing of materials and development of documents | community essay solicitation

Tribulation will not bring you down 、 Rise up at the right time . The whole country is united 、 It is a special moment for us to do a good job in the prevention and control of the COVID-19 .

Hello everyone , When the epidemic occurs , Many people may be forced to stay at home and work , It's good to work from home , But many resources are still in the company , So there are still many inconvenient places in the rear , How to solve these problems , If we want to solve the problem , Then the best way is to sort out all the problems first , Now let's see what the problems are ？

problem

When everyone works at home, it is a headache to edit relevant documents or modify relevant materials ：

• Some of our relevant development and design documents , How to realize collaborative editing ？ How to edit ? How to merge and inform everyone to modify in real time , Complete relevant documents ？

• dependent API Design documentation ： Generally speaking, it will be divided into external oriented OPEN-API file , Design interface definition document for internal developers . How to achieve effective and reasonable documentation , And everyone can edit and adjust at the same time ？

• Control of relevant requirements documents , Not everyone can forward everywhere , Edit the modification trace , Nor can it be unified , And some notes , Business cannot be written directly, leaving traces , In addition, the ability to notify people is also difficult to achieve , Notify everyone .

answer

Have a problem , We're going to solve the problem , Right , Next, I will focus on these issues , Summarize relevant implementation schemes .

• First , How to realize the collaborative editing of related development and design documents ？ There are many ways , For example, to our current company commonly used coding、wiki as well as lark Self contained editing document .

• coding, It mainly adopts a developer oriented perspective , More time , We will use it to write some design documents , Including architecture diagram and interface design documents related to internal development , Flow chart and other operation control .

• jira, I believe you are no stranger , It is aimed at some design documents related to system functions among internal developers , It's a coding Write internal documents of relevant documents , There are also some related information registration , We will also adopt jira One of the reasons for writing this method .

• lark The editor's tools , We're going to use lark Communication tools of , In fact, it is what we often call flying book , It actually supports related online documents , It is very similar to the function of nail , adopt lark Push to the cross department group , Multiple departments can mark abnormal data , Then divide the personnel to follow up and solve the problem , Realize data-based online collaborative office .

• For external OPEN-API The document adopts ,vuejs Write relevant api The page is displayed , That is, the relevant development page , Although it requires a certain development cost , But because it is globally unique , We used git To maintain , Therefore, we can realize relevant collaborative processing and public development adjustment . On the other hand , We're going to use jira Or is it coding To develop design , The real appearance can be internalized and shared , Instead of the traditional word file , It's convenient and convenient .

• The third point , Actually, it's using lark To deal with , because lark The documentation that comes with you , It is to support the selection of relevant personnel within the enterprise , In this way, there is no need to inform the corresponding personnel , It provides the relevant @ After selecting personnel , Send notification information directly , In addition, relevant comments can be added to the document , It's really very convenient ！

I hope we can tide over the difficulties , Defeat the epidemic ！