i18n Integration

[mateodaza]

Based on a request from the governance call lead by @divine-comedian we'd love to implement translations for all texts on the dApp to allow multiple languages

Using this guide we'll start with Spanish as an alternative language

@MohammadPCh @alireza-sharifpour @RamRamez tagging you to keep you on board

[divine-comedian]

one note here is that our links to documentation inside the app should go to the spanish version

https://docs.giveth.io/es/

the slugs remain the same but only prefixed by /es/ for example

https://docs.giveth.io/giveconomy/ -> https://docs.giveth.io/es/giveconomy/

[MoeNick]

I have questions about it @mateodaza :

1. Does it have a design effect? I think there may be a place where users select which language they want and see the result.
2. in order to add moe languages in the future, don't we need to manage them by the backend? so we need a structure to provide different language versions, especially content which come from the backen, like toast messages,
3. in DevOps point of view, how can we implement a policy to show the default language in different parts of the world?

[mateodaza]

Hey @MoeNick

1. Yes totally, we could let the user set the language in his settings and also display somewhere, usually it's in the footer. I'm currently checking browser's default language to test things out
2. Yes, I started with static content but that's a good second stage. Essentially we'll send the language through the impact graph query and that's it. @CarlosQ96 or @mohammadranjbarz can work on it eventually. I didn't wanna pressure on this yet as it's not hot priority and they were full handed
3. Browser provides this info :) and also we can allow the user to set it up

[MoeNick]

I think we should also engage @mosaeedi and @Tosinolawale in this issue for the design of changing the language.