When using fragments Page Creator may need to localize a fragment configuration field for that it shows different content for each language.
The goal of this story is to allow a fragment developer to add localized fragment configuration field so that Marketers can localize the content of the fragment. A marketer will then know that a field is localizable thanks to a visualization field (like a flag, or text label).
Given a fragment configuration needs support for localization.
Custom configuration field
Given the fragment developer has defined a new custom configuration field for a fragment
When a fragment developer marks a config field as localizable
- the config field can be localized
- the Page Creator can vizualize that the config field can get a distinct value per local
Schema definition of Page Fragment
The export/import JSON definition will be modified a test should be included to make sure the definition is updated and export the localizable = true config field. Also we need to make sure the documentation is updated.
|Test Scenarios||Test Strategy||Kind of test||Is it covered by FrontEnd ? (JS-Unit)||Is it covered by BackEnd ? (unit or integration)||Could it be covered by POSHI?|
|View localizable fragment configuration field value in translated languages||Hign||Manual||No||Yes||Yes|