pournasserian
commented
1 month ago @reactmatz we have an open issue for localization to develop and support multiple languages here: https://github.com/fluentcms/FluentCMS/issues/365
First, we should implement JSON based localization for backend and frontend as well.
Then we should change all file containing static text/content and create a base fallback JSON file for en-US.
The last part is translating a couple of JSON files in other languages.
Any idea other than that?
Hello, i'm Matheus
I am interested in translating the FluentCMS documentation into Portuguese to make it more accessible to Portuguese-speaking users. I have outlined two potential approaches for this translation effort:
Approach 1: Translate Directly in My Fork Process: I will create a fork of the FluentCMS repository and translate the documentation and project files directly in my fork. Outcome: Once the translation is complete, I will request that a link to my fork be added to the original repository, providing easy access to the translated version for the community. Approach 2: Submit Multiple Pull Requests (PRs) to the Original Repository Process: I will clone the original FluentCMS repository and create separate branches for each set of translations (e.g., README, documentation files). I will then submit multiple PRs for each translated section. Outcome: This approach will integrate the translations directly into the main repository, benefiting all users. I will work closely with the maintainers to review and merge the translations. Request for Feedback I would appreciate your feedback on these approaches and any preferences you might have. My goal is to contribute effectively to the project and ensure the translations are beneficial to the community.
Thank you for considering this proposal. I look forward to your response.