Repeatable content for simple property editors

[bjarnef]

Sometimes we need to control image (or other content) specific to responsive layout, e.g. Mobile, Tablet and Desktop.
We could add three properties "Image Mobile", "Image Tablet" and "Image Desktop", but sometimes I think it would be simpler with a single property "Image" and then defining breakpoint configuration in property editor, wrapping an existing property editor.

With image it can be solved using different crops as long it is same image, but we have sometimes has the need to control an embed, video, text or similar per breakpoint (and eventually used device detection in code).

Nested Content / Block List could be used, e.g. adding three blocks, but it would probably need to be three different blocks to know its type and if it is for Mobile, Tablet or Desktop.

Perhaps a combination of repeatable textstrings (perhaps repeatable numbers, dates etc. in future) and Nested Content / Block List.

An example could be something like this.
Perhaps listed as tabs with icon/name + textbox under each tab panel.

[
   {
       "alias": "mobile",
       "icon": "icon-mobile",
       "name": "Mobile",
       "value": "This is a text on mobile"
   },
   {
       "alias": "tablet",
       "icon": "icon-tablet",
       "name": "Tablet",
       "value": "This is a text on tablet"
   },
   {
       "alias": "desktop",
       "icon": "icon-desktop",
       "name": "Desktop",
       "value": "This is a text on desktop"
   }
}

Not necessary just for breakpoints, but could be anything where one want to define and key/alias and connect it with a specific value.

Vorto did it it some way connecting a value to a culture and similar for Multilanguage Textbox

In these use-cases I think it would be a bit overkill with Block List and not easy to target a specific entry/item unless one add a key/alias to each item, but often we don't want content editors to worry about this.

Key/alias could be:
Culture/Language code, user-defined alias, etc. The culture/language code could be hard-coded, but may be useful to select existing BE languages.

Value could be:
String, number (integer/decimal/float), datetime.

[skttl]

Could be a combination of these package ideas
leekelleher/umbraco-package-ideas#47
leekelleher/umbraco-package-ideas#48

[leekelleher]

From a community perspective, I'd started going down this route with the Textbox List editor in Contentment, but then ended up sticking with textbox inputs (probably for simplicity and my own specific needs at the time).

I definitely like the idea of a repeatable tuple-type editor, could be quite exciting! 😀
Probably best prototyped as a community extension first, for exploration/iteration, etc.

[bjarnef]

@leekelleher perhaps it is easier to re-use input component and input type in the new backoffice.
Often a repeatable textstring array, but could also be list of email, url, number (int/decimal/float), date input fields.
I guess it could possible make the existing repeatable textstring property editor obsolete at some point.