In theme.json templateParts supports two values: name and area.
name matches with the filename for a template part. When viewing Site Editor > Template Parts, available parts are described using the value for name. This can result in an "unfriendly" label for each part, especially if using overly descriptive names.
chthonic-ds commentedSep 10, 2021
What problem does this address?
In theme.json
templateParts
supports two values:name
andarea
.name
matches with the filename for a template part. When viewing Site Editor > Template Parts, available parts are described using the value forname
. This can result in an "unfriendly" label for each part, especially if using overly descriptive names.For example, the following in theme.json:
...currently displays like this in the Site Editor:
What is your proposed solution?
Is it possible to support a third value in
templateParts
, please? Perhapsdescription
could work as the key.This would allow for the following:
The text was updated successfully, but these errors were encountered: