Smartling has a tool (CAT) to assist translators that live-overlays their WIP translation strings on top of the actual site being translated.
This works fine for us with hard-coded Django views, which usually ship in en-US immediately, and then can be localized afterwards. CMS-backed pages, however, present a new workflow that we may need to handle
This is a placeholder Issue.
We need to:
[x] Confirm whether we need to support CMS-backed pages in the Smartling CAT
[x] Decide a workflow (e.g. which site will it be based on - likely production)
[x] Define and solve edge cases, including translating pages that are not yet published ( ie, are still Draft ) without requiring localizers to have CMS login acccess, because they will not all have this
stevejalim
commented
5 hours ago
Smartling has a tool (CAT) to assist translators that live-overlays their WIP translation strings on top of the actual site being translated.
This works fine for us with hard-coded Django views, which usually ship in en-US immediately, and then can be localized afterwards. CMS-backed pages, however, present a new workflow that we may need to handle
This is a placeholder Issue.
We need to: