Improve translation workflow and CMS handling

[decentralauren]

Business Description

Overhaul of how we do, review, store and serve translations across products & SDKs

Issues with current implementation:

• We are maintaining storage of separate translations for each product
• Translations are not being managed / maintained by product or comms
• New features or updates to existing features are not being translated

Proposed Solution: TBC

Detailed Description of Functionality

Technical Implementation

*Outline the technical approach for building the feature. This section is typically filled out by the development team or can contain suggestions. (dev team: @johnsmith-gooddollar @sirpy @L03TJ3)

• [ ] (What api's / sdk's could possibly be used)

Acceptance Criteria

Specify criteria that will be used to determine if the feature meets the requirements and functions correctly.

• [ ] (Should include a list of testing points for QA how to verify design/functionality)

[sirpy]

@decentralauren probably under the wrong repo (GoodServer)

[decentralauren]

@sirpy thanks - sorry about that. can you move it? I'm unable to do so with my GH permissions.

[L03TJ3]

@sirpy why is this a wallet issue? I don't think we will change this for wallet v1 at this point. could be we copy it over for an item on wallet v2 as well

[sirpy]

@L03TJ3 you are probably right. @decentralauren What products would this be relevant to