investigate the possibility of allowing the client to create static content easily and converting it for a static translation process

[osahon-okungbowa]

We need to investigate possible approaches for having a client-friendly intermediate step that allows the less-technical members of the client's team to provide updates to the static translations of the Fronted App.

example of an approach: Provide a CSV file with columns for english and arabic translations. Whenever they update the CSV file, they push it to a repo (this could be a new repo to handle translations). Once it is pushed to the repo, Githiub Actions runs a job to translate the CSV file to the appropriate json translation files. Then it triggers a Frontend App Deployment with the new update.

[anuveyatsu]

One simple and scalable (no code to maintain) option would be using VS Code version of github:

https://github.dev/FCSCOpendata/frontend/blob/main/locales/ar/common.json

cc @osahon-okungbowa

[osahon-okungbowa]

@anuveyatsu so they just edit and it autosaves? Then they trigger a deployment??

[osahon-okungbowa]

@anuveyatsu is this the only solution you want to provide for now?

Please note: i'm leaving the analysis and discussion of this process to you. Kindly discuss with Hatem during our meeting