Contribute to the Docs ​

I'm glad that you are interested in contributing to Fresns document translation. Before making the contribution, please take a moment to read the following introduction:

Introduction ​

Fresns supports multiple languages at the data stream level, and various languages can be added at ease without modifying main programs, themes, plug-ins and clients. It supports 187 languages in 239 countries/regions around the world (the data strategy conforms to the laws and regulations of all regions in the world), and supports any language and time zone with a simple configuration in the background.

Although we support multiple languages, language packs still need to be translated. Feel free to use your language to support the development of Fresns ecosystem.

Fresns Website ​

All the pages you see at present fall into the category of official website. They are written based on Markdown files and compiled by VitePress site generator.

• Code Repository: https://github.com/fresns/docs/
• Language Files Directory: /wiki/

Control Panel ​

The language pack of the main program (back-end) management center is the file of the main program code warehouse. By means of Pull Request, you can correct the errors of the existing language files or add new language files.

• Code Repository: https://github.com/fresns/fresns
• Language Files Directory: app/Fresns/Panel/Resources/lang/

Client Language Packages ​

Language pack with "Language Tag" as the key name is stored in the database configuration table, which is obtained by the client through the interface, and then parsed for local use by the client (see multilingual setting function). See the key value of configuration table language_pack for the language identification name, which is the basic language identification name of Fresns initialization. Operators can add custom language identification names according to the actual situation of the client.

• Code Repository: https://github.com/fresns/docs/
• Language Files Directory: /language-pack/

Participate in translation by means of Pull Request, and we will update the new language pack to the main program database when the main program version is upgraded. In order to reduce the workload of writing documents and ensure the consistency of public data, this page uniformly writes the same parts of API documents into data structures.