The UI only supports variations for headlines at this time, and they are pre-defined by Arc.
Supporting either dynamically added variations directly in the editor for each of these fields OR settings-defined variations at the field-level would give organizations more flexibility when inputing data.
This is especially important for new clients during the migration process, as the ANS supports variations on these fields without restriction and it's confusing when trying to reconcile where data should be migrated to and still be editable in the UI.
Guest
Currently, the following fields in the Story ANS use the dictionary type:
headlines (https://raw.githubusercontent.com/washingtonpost/ans-schema/master/src/main/resources/schema/ans/0.10.9/traits/trait_headlines.json)
subheadlines (https://raw.githubusercontent.com/washingtonpost/ans-schema/master/src/main/resources/schema/ans/0.10.9/traits/trait_subheadlines.json)
description (https://raw.githubusercontent.com/washingtonpost/ans-schema/master/src/main/resources/schema/ans/0.10.9/traits/trait_description.json)
The UI only supports variations for headlines at this time, and they are pre-defined by Arc.
Supporting either dynamically added variations directly in the editor for each of these fields OR settings-defined variations at the field-level would give organizations more flexibility when inputing data.
This is especially important for new clients during the migration process, as the ANS supports variations on these fields without restriction and it's confusing when trying to reconcile where data should be migrated to and still be editable in the UI.