As part of template translation (T139332), users may find situations where editing becomes more complex than just filling information in the corresponding fields. This can be produced by the complexity of information in the template or the lack of metadata about it.
In particular, this ticket is intended to provide details about how to support the following circumstances:
- **Manual mapping.** Mapping parameters manually when there is not existing mapping between the fields in the source and the target templates.
- **Recursive template editing.** Templates may contain fields which contain a template. It should be possible to edit those.
- **Compact unused fields**. The main focus for template translation is to adapt those fields with information in the source template. The translated template can present other fields in a more compact way to avoid them getting in the way.
# Proposed solution
**Manual mapping**
When there is no mapping between the source and the target template, users can define such mapping. Similarly to what is done with paragraphs in a translation, users will add fields one by one and the'll indicate the corresponding mapping with the target template.
{F4485936}
- Initially no fields are added.
- Users are invited to add the field they hover (or the initial one if none has been added.
- Corresponding fields are highighted.
{F4485954}
- Once a field is added, the content is adapted by following the usual approach (which users can change).
- Users need to select the target field.
{F4485942}
- Selection aids are provided to easily select the mapping.
- Field names are shown with one line of the description to show additional context.
- Unassigned fields are shown on top.
{F4485957}
- Once the mapping is stablished, users are able to change it to another field.