You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m very much appreciative of Craft 5’s multi-instance field capability whereby:
Most fields can be added to a single layout multiple times.
And that any field given a layout-specific label and handle can be inspected in its slide-out to see what its canonical source field is.
However, when building out layouts with many fields, and then entry type variants that derive but also diverge from such a source layout, seeing the wood for the trees involves clicking into each layout field definition to check what its source field is.
When editing a layout there is, by default, an under-utilised layout meta area on the right (on wide viewports) which could report a mapping of layout-specific field name to source field name:
For example, suppose source fields such as:
Handle
Field type
Settings
singleLine
Plain text
multiLine
Plain text
Multiple lines
htmlStandard
CKEditor
‘Standard’ config
switch
Lightswitch
OFF
switched
Lightswitch
ON
codeMultiLine
Plain text
Multiple lines and monospace
…and a layout which deploys:
Layout field handle
Source field handle
firstName
singleLine
lastName
singleLine
jobTitle
singleLine
bio
htmlStandard
manager
switch
…something like the latter table could be reported as read-only information in the layout meta area, thus making reviewing and managing layouts a little easier.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I’m very much appreciative of Craft 5’s multi-instance field capability whereby:
And that any field given a layout-specific label and handle can be inspected in its slide-out to see what its canonical source field is.
However, when building out layouts with many fields, and then entry type variants that derive but also diverge from such a source layout, seeing the wood for the trees involves clicking into each layout field definition to check what its source field is.
When editing a layout there is, by default, an under-utilised layout meta area on the right (on wide viewports) which could report a mapping of layout-specific field name to source field name:
For example, suppose source fields such as:
…and a layout which deploys:
…something like the latter table could be reported as read-only information in the layout meta area, thus making reviewing and managing layouts a little easier.
Beta Was this translation helpful? Give feedback.
All reactions