Replies: 6 comments 6 replies
-
On paper it makes sense that titles in entry cards and chips always link to the entry's dedicated edit page. In practice, there are several use cases where authoring content via slideouts is the preferred workflow – this being a very good example – and in those cases, a lot of authors definitely struggle to learn/remember not to click the entry title – inevitably getting tripped up from time to time when they end up navigating to a nested or related entry's edit page without meaning to. (In my experience, this is particularly frustrating when authors are working in live preview, and accidentally click on a card/chip title). I've been wondering if it'd make sense to introduce a "Disable title link" setting for Matrix and other relational fields, in cases where the slideout AX is considered to be the preferred way to edit the nested/related content. That idea feels a bit clumsy to me though, maybe there's a better way to solve this? |
Beta Was this translation helpful? Give feedback.
-
That's along the lines of what I was thinking, something to configure on Matrix/relational fields to improve the author experience based on the use case 🤔 |
Beta Was this translation helpful? Give feedback.
-
@gateszies The UX problem you are describing is not solved entirely by this, but do note that Matrix fields can have their own preview targets, so "block" (nested entries) drafts can be previewed. Maybe an alternate/additional solution would be to surface the revision and drafts functionality (creation, switching between revisions etc) in slideouts? |
Beta Was this translation helpful? Give feedback.
-
@thupsi Not sure I'm following -- I don't currently see a way to preview a draft on a nested entry when landing on the screen below 👇 |
Beta Was this translation helpful? Give feedback.
-
@brandonkelly A few different suggestions for configuring these editing options below👇 |
Beta Was this translation helpful? Give feedback.
-
@brandonkelly Updated proposed UI for opening title links in slideout below 👇 |
Beta Was this translation helpful? Give feedback.
-
Description

We use matrix fields to create a page builder experience, with each entry type mapping to a section used on a page (see below).
Our authors have run into some confusion when creating drafts in this builder. We'd like them to use the slide-out feature that the new Matrix field offers. This allows them to Create a Draft on the entire entry, slide out and edit different blocks, and view those various changes in Live Preview. This functionality works well, see below.
matrix-draft-behavior-slideout.mp4
They run into issues when they open the block in a new tab and create a draft on the block instead of on the page. They are unintentionally landing in this flow by clicking on the text link for the block (ie
2024 Holiday Collection
) which takes them to a new tab instead of clicking on the card modal to trigger the slide-out. This misclick leads them into an experience where they Create a Draft on the block, have no way to preview it in their current tab, and also can't preview it when they go back to the entry and use Live Preview. See below for that flow.matrix-draft-behavior-text-link.mp4
Suggestions
It's a bit too easy for authors to wind up in the block draft mode, when in the context of a page builder, we only want them to be using a page draft. I can see the advantage of offering both draft modes but it'd be great if we could have more control under the hood on how this is surfaced to authors depending on the use case for the Matrix field. Could there be additional configuration for Matrix fields to decide whether a block in a Matrix field should exist in an individual context (block draft mode) or if it should always exist in the context of the page (page draft mode, like a page builder).
Some of this is educating authors on how to interact with the CMS but it seems like an easy enough mistake to make that it'd be great to refine the experience a bit. Open to any ideas or suggestions!
Beta Was this translation helpful? Give feedback.
All reactions