-
Story
-
Resolution: Obsolete
-
Neutral
-
None
-
None
-
None
Phase 1: Ability to choose a language and create a translation
User stories:
As an author I can enter content in multiple languages.
As a developer I can configure a content editor for multiple language support.
Acceptance criteria:
- Support the Magnolia standard way to enable multilanguage content in the Stories app --> Should be covered by
CONTEDIT-389- Outline fields that do not have the i18n property should have the same value in every language. Rationale: Outline fields such Author, Date and Location are often not translated. They have the same value across translations.
- Validate user input in outline fields the same way we do in a typical form. When a user switches between languages Magnolia should validate the input. For instance, alert the user if a required outline field is empty.
Out of scope from this ticket
- Provide a language selector dropdown in the lower left corner of the editor subapp, see design –> Now
CONTEDIT-393 - There is no link between blocks of different languages --> Now
CONTEDIT-394
Acceptance criteria
- is cloned by
-
CONTEDIT-393 Provide a language selector dropdown
- Closed
-
CONTEDIT-394 Create UI test. Ability to edit the text blocks and it structure at the language level
- Closed
- is depended upon by
-
CONTEDIT-208 DOC: i18n references in content editor context
- Closed
- relates to
-
CONTEDIT-121 Copy story from one language to another
- Closed
- Wiki Page
-
Wiki Page Loading...
(4 mentioned in, 1 Wiki Page)