Display values for RichText labels

[dmytrob]

Loving the RichText labels functionality, but missing the ability to have two values per label, - a key/technical one and a user-friendly one, that shows up in RichText UI dropdown.

Use case, - the typography in our design system is defined as [ "hero", "title", "subtitle", "body", ... ] which is what we have define for out typography labels, but it's quite technical and not always immediately obvious for the non-technical end-users. We would prefer to be able to configure the labels somewhat like this: [ { name: "hero", display: "Hero (H1)"}, { name: "title", display: "Title (H2)"}, ... ], so that we can customize the display values of the labels to be more understandable without compromising the tech of our app. Trying to define it like this in content-type JSON currently breaks the RichText for the field (it doesn't show in the UI), so it looks like it's unsupported at the moment.

[Phil (Phil Snow)]

Hi Dmytro,

Welcome to the community.

As you've seen this isn't possible at the moment, but we are tracking a similar feature request for select fields and I suggested a workaround suggested using regular expressions there:

Iterating Select values in template from other Document

Hey Srini, At the moment it isn’t possible to define a label and a separate value. The @features-team have an open feature request for this, if/when we ever make a change to this behaviour we’ll update you in this thread. For now you will need to build the values into your website application. Sorry for the inconvenience. One solution might be to add values like: Downtown warehouse [33] Then in your project use regular expressions to get only numbers inside the brackets: or js slice to …

You would need to combine something like that with the HTML Serializer since this is in the Rich Text field:
https://prismic.io/docs/technologies/html-serializer-javascript

I'm tracking this as a separate feature request also as it's slightly different than the original request. Though I don't think the product team will implement this in the near future as they are planning an overhaul of the Rich Text field and this would have to be considered alongside that work.

I hope this helps,
Thanks.