-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the "Title" field behave like all other fields in the Admin UI #3953
Comments
I also never understood why the field has to be displayed in every tab. It has confused clients of mine too because they didn't understand that this was always the same field. They tried to change the title for different tabs. |
I already postet this as a CSS-only workaround(!) in Discord: [id^="tab-"]:not(:first-child) {
position: relative;
margin-top: -81px;
background: #fff;
} This only hides the title visually by overlaying the title field with the tab content. But there is no other property in the markup to influence the title field depending on the selected tab. A real solution without custom hacks would of course be much better. |
For me it's fine to have this field in every tab. But maybe it's fine to put it outside the tabs to make it more clear. Understand the problem (UX). +1 for a better solution but not the solution like in post one |
Right direction! |
@dennisfrank this UI is much clearer about Title being the same field in different tab states. I however wonder about the balance of pros and cons of repeating the field. Having it in one place only and not repeated makes it easy to associate with that one place and eliminates confusion. Having it be accessible from everywhere is not a common ui pattern and still a potentially confusing for admin users. Real world-wise, It is not common to have redundancy of controls. As in, for the same light to have switches in different places. It may happen at the two ends of a long hallway. Do we have the equivalent of a long hallway here? If this is the case, we already have a place for fields accessible from all tabs — in the right hand sidebar along with the slug, date and comments. Lastly, I am curious about the history behind the decision to make it available everywhere in the first place. Did admin users need access to title change more often than anything else? |
There's an existing issue for moving the title field outside/above tab content: |
I've written a simple plugin that shifts the title field to the sidebar: https://plugins.craftcms.com/craft-title-to-sidebar. |
Description
Currently, the "Title" field is repeated in each of the tabs of an entry's admin panel. It also cannot be assigned to a tab in the field layout in the settings section.
Making the Title field behave like the rest of the fields would be an improvement to the consistency of the UI and UX of the CMS. Right now Title behaves differently... It could still be mandatory, but position-able within the content tabs.
It has confused users because they didn't understand that this was always the same field.
Steps to reproduce
Proposed improvement
Make it possible to assign the Title field to a field set just like any of the other fields. If necessary, make it non-remove-able.
Additional info
The text was updated successfully, but these errors were encountered: