This would likely be a big change, but thought I'd throw it out there, perhaps to be considered with #1524
Field configuration can be complex, especially with a heavily configured Matrix field.
It would be ideal if one could create a field and use multiple instances of it in a single field layout.
Use-case:
A fairly common practice for module page building seems to be including a mega "Content Matrix" field, with many block types for all types of content. This has a breaking point when you need two independent sets of these blocks (e.g. Content Matrix Main, Content Matrix Sidebar).
Duplicating a second field is tough, and keeping them in-sync over time is even harder.
This could potentially also be a solution for issues like #806, as each field instance could have it's own title and instructions.
I toyed around with the idea of creating a plugin with a "Proxy FieldType", where the only field setting was a field selection of the field you wanted to mirror. Works great for things stored in content, but obviously gets complicated with Matrix and others, which is really what you'd want it for. Let me know if you think this might be do-able and/or more appropriate via plugin, or if it is something you'd consider for core/v4/fantasy land.
This would likely be a big change, but thought I'd throw it out there, perhaps to be considered with #1524
Field configuration can be complex, especially with a heavily configured Matrix field.
It would be ideal if one could create a field and use multiple instances of it in a single field layout.
Use-case:
A fairly common practice for module page building seems to be including a mega "Content Matrix" field, with many block types for all types of content. This has a breaking point when you need two independent sets of these blocks (e.g. Content Matrix Main, Content Matrix Sidebar).
Duplicating a second field is tough, and keeping them in-sync over time is even harder.
This could potentially also be a solution for issues like #806, as each field instance could have it's own title and instructions.
I toyed around with the idea of creating a plugin with a "Proxy FieldType", where the only field setting was a field selection of the field you wanted to mirror. Works great for things stored in
content, but obviously gets complicated with Matrix and others, which is really what you'd want it for. Let me know if you think this might be do-able and/or more appropriate via plugin, or if it is something you'd consider for core/v4/fantasy land.