Localization Pre-MMF research

[jpvajda]

As we migrate the docs site to gatsby we need to define our approach for localization for the new site. This task is to do some preliminary investigation into how we will approach localization short term and long term.

Short Term

• Evaluate the current technology approach with the Drupal site to see if there is a way to use the existing vendor solution for our localization approach with the new site.

Long Term

• Evaluate the long term technology approach and determine an iterative way to move forward.

[caylahamann]

Some research from this morning:

I found a repo from OneLink that uses the proxy and React to localize content on the page. It seems from this it is possible to first implement with OneLink for the short-term, then eventually have our website conditional render from Smartling, and then eventually have Smartling implement with Github. The repo uses react-intl for localization and provides the content via a context provider.

The repo uses Node, Express & GraphQL as the server, which leads me to believe that we would be able to use this as a basis for our localization approach with OneLink.

[zstix]

@caylahamann Sorry for being so late to coming back to this.

Do you know if we need a backend server to make the proxy work? Due to the docs site being static, we wont have the ability to anything with express-request-language.

If we don't know, we can build that research into our MMF.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.

[jpvajda]

This is SO DONE. 😄