Languages support

Created: 12/27/2016 | Updated: 8/24/2018 | Status: Published

Language support between content site and trading platform
 
our main goal is to be able to communicate between the trading platform site and the content site even after user has selected a different language.
 
This is the main  idea:
 
- user select a language to display in the content site
- user click on a link that send him to the platform site
- user get to the platform site and see it in the language he already chosen on the content site
 
- same idea when user select a language in the trading platform and linked to the content site
 
To achieve  that we need to take some actions in the trading platform and content site:
 
Trading platform
The trading platform - trading.xxx.com uses a simple automatic url structure for language support.
 
lets say you default language is EN, all of your EN pages in the trading platform and content site will stay the same with no changes.
E.G:
in the trading platform url for EN will be: trading.yourdomain.com
in the content site url for EN will be www.yourdomain.com (on content.yourdomain.com - depends on your content site domain)
 
 
when the user select a different language, let's say Spanish, the trading platform automatically changes all of the links from trading platform to content site and adds a language code to every link.
 
E.G - user selected Spanish so all links in the trading platform site will be change like so:
www.yourdomain.com/es/ - for the content site home page
www.yourdomain.com/es/contact-us - for a content site inner page
 
this take care of links from the trading platform to the content site.
 
 


 
 
Content site
 
in the content site you need to support this url structure for language support.
if you are using Wordpress for the content site we recommend a plugin call WPML that automatically generate you this url structure for different languages .
 
so when a user will be sent from the trading platform to the content site page he will get the right page in the right language.
 
 
 
 
1.    The first thing with should do is take care of translated pages in the content site.
 
 
Now we want to translate the site to ES, so that means that the ES version of the page must be with the same url only with different language code.
 
E.G
www.yourdomain.com/contact-us - EN
www.yourdomain.com/ed/contact-us - for ES
www.yourdomain.com/fr/contact-us - for FR
 
as you can see – we maintaining the same url for all pages in other languages. We only change the language code
 
 
 
2.    The next step we should take is to care of links from the content site to the trading platform.
 
E.G we have a "trade now" button in the content site navigation menu,
this link will be "trading.yourdomain.com"
this is good for your default language.
 
Now we want to translate the site to ES, so that means that the ES version of the page must be with the same url only with different language code.
 
E.G
 trading.yourdomain.com/contact-us - EN
 trading.yourdomain.com/ed/contact-us - for ES
 trading.yourdomain.com/fr/contact-us - for FR
 
as you can see **and this is the most important issue*** – we maintain the same url for all outgoing links and only changed the language code.
the url of a page will always stay the same in all different language, we just change the language code at the beginning of every page URL