Improve Revisions UI and Relationship / Modal UI #1440
TomSmedley
announced in
Roadmap
Replies: 1 comment
-
I think these are all great ideas. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
At the moment, with Revisions, you get quite a technical layout to see the differences which is hard to understand for the client. It's using a raw value rather than a formatted value:

What has a really good revision experience is Contentful and maybe Payload can take from this experience.

What it lets you do is choose which fields you want to roll back it also uses what is rendered on the edit screen. I'm thinking Payload can do something similar where rather than rendering the value, it renders a field as it would in the editor, however, it will be with
pointer-events: none
and be wrapped in a selectable box in which they can choose with value to carry over from the previous version.Here is a mockup of what I was thinking:

I was also thinking using the remove icon from the upload field for the modal will allow for the same visual language.

This is just a personal one but I felt like the remove all button felt a little lost next to the drop down icon as one was an indication of the field being a drop down. By taking on the style of the "Add new" functionality, it becomes clear it's an actionable button:

Beta Was this translation helpful? Give feedback.
All reactions