The first step we took was creating a thesaurus, since it is the basis of the entire translation. The format of the thesaurus gives us:
Community Edition core development plans are built in such a way that you can’t just take standard ready-made documentation and translate it. First, we evaluated which content definitely will not change in the near future. Then we determined translation priorities and approximate deadlines for certain parts of the documentation.
Since our project team is small and we do not use single source documentation systems (such as LaTeX and DITA), most of the operations at the current are done manually. Switching to a single source system could solve most arising issues, but the transition and training of employees may take 3 to 4 months.
Taking into account all the above, we have established the following working scheme: