[CONTEDIT-389] Investigate how to internationalize a story Created: 14/Sep/17  Updated: 07/Oct/21  Resolved: 17/Aug/21

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: i18n Stories App
Story Points: 13

 Description   

Investigate how to store stories (Content Editor content) in multiple languages. The way you store the content will impact upcoming tasks such as activating a single language.

Consider:

  • Storage of multilanguage content.
    • One option would be to mimic what we do for personalized variants.
    • Be careful of creating yet another mechanism to store content. We will need to personalize the content too.
  • Requesting a particular language
  • Rendering language-specific content (ie. wrap the story)
  • Scenarios such as two folders of stories where one is translatable but the other is not. (not a requirement but worth thinking)

Generated at Mon Feb 12 00:19:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.