I am designing a new feature for a CMS my company uses. A few things you should know:
- We have content editors working mainly on adding pages to the system. We have thousands of pages, and no one editor knows them all.
- There are also categories, that group several pages.
- We use aliases to fetch the right page or category for the end-user. Aliases must be unique! You can't use the same alias for 2 different objects (pages or categories).
- Aliases are just one field on a form of with dozen other fields. Most of the time content editors fill out these entire forms dozens of times a day.
The feature I'm adding is a contextual message (ie. appears in real time, not after sending changes to the server) that appears when the user has typed in an alias that already exists on some other page.
This is what I currently have:
I have a feeling that this feature has a few problem. Please help me fix them (or explain why they are not as problematic).
- Catching attention - I have a feeling that the message isn't prominent enough. Editors won't be able to submit the form without choosing one of these actions, but it's better to notice it before submitting.
- Options hierarchy - I'm afraid I'm offering too many options here, but all of them are possible. The first option will get selected most of the times, but we want editors to consider the three actions and choose the right choice. Is there a different way to present these which is more digestible but doesn't make the decision for the user?
- Layout - is there a better way to layout this message? I don't want to turn this into a modal element (will break their workflow too often). Also, take into account that there are other similar fields above and below. We're using Bootstrap, so I prefer solutions from there.