[MGNLUI-4570] Translatable content type fields Created: 16/Apr/18  Updated: 17/Aug/18  Resolved: 17/Aug/18

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Ngoc Nguyenthanh
Resolution: Done Votes: 1
Labels: None
Σ Remaining Estimate: 0.25d Remaining Estimate: Not Specified
Σ Time Spent: 9d 5.5h Time Spent: Not Specified
Σ Original Estimate: 0.5d Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-4571 Transfer i18n setting from property d... Sub-task Closed Hieu Nguyen Duc  
MGNLUI-4572 Check i18n setting with composite and... Sub-task Closed Oanh Thai Hoang  
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)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Content types foundation
Sprint: Saigon 151
Story Points: 8

 Description   

User story:

As a Developer, I can define which fields in a content type are translatable

Acceptance criteria:



 Comments   
Comment by Mikaël Geljić [ 23/Jul/18 ]

Here's a draft including an example with a composite group (aka sub-model):

Given the model below, let's consider two use cases for composite groups:

model:
  properties:
    - "name"
    - "position"
      type: Job
  subModels:
    "Job":
      properties:
        - "title"
        - "organization"

A. Enable `i18n` on the position property

* mika
  - name: Mika 
  * position_fr
    - title: Ingénieur Logiciel
    - organization: Magnolia International     # assuming we don't really translate organization name, but here we could
  * position_hr
    - title: Softverski Inženjer
    - organization: Magnolia International

B. Enable `i18n` on the title property

* mika
  - name: Mika 
  * position
    - title_fr: Ingénieur Logiciel
    - title_hr: Softverski Inženjer
    - organization: Magnolia International     # common for all languages here

We do not consider the case of combining i18n on both group and sub-property level, because it doesn't bring additional value, and would only result in some unreachable properties.

Generated at Mon Feb 12 09:17:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.