Originally submitted on Github
Problem/Motivation
Recent interviews and research exposed pain points around Drupal's admin experience of looking and feeling dated. Tags and entity reference fields are currently representing selected elements just by text and its id, giving a very poor visual experience.
Proposed resolution
Implement new Tag / Entity reference field style to create a favorable first impression of Drupal for evaluators and a better user experience for site authors. Styling the same information in a more appealing and self-explanatory way will also help users understand the UI faster and lower the cognitive load.
Specs:
@todo
Remaining tasks
- Define how the new styling will be rendered
- Add design detailed specs
- Update patch styling to include time inputs
- Accessibility review
- RTL review (Right to left)
User interface changes
@todo
Test Pages
@todo
Comments
Comment #2
antonellasevero CreditAttribution: antonellasevero commentedComment #3
saschaeggiComment #4
ckrinaRemoving outdated link to Figma and minimizing some summary info.
Comment #5
lauriiiWhat is this issue for? Would it be possible to get more background information about the component in the issue summary and/or link to Figma?
Comment #6
ckrinaThis one is to update the visual styles for tags with a new design, but we're stopping this until all the other MVP components are ready since it clearly implies much more than just CSS. Here's the design proposal:
Comment #7
ckrinaUpdating the issue summary. The title probably needs to be changed once we know the final implementation to be able to render all the info.
Comment #8
ckrinaComment #9
huzookaComment #10
ckrinaComment #12
oliversiegel CreditAttribution: oliversiegel commentedI think this is a fantastic issue, and well described. Yes, lowering cognitive load for the user!! So important!
Actually I really need this for my project/Drupal site. It's a crucial building block to it. Taxonomy is an important native Drupal feature, but I need it to be user friendly and better looking. Just as proposed here.
Comment #13
No Sssweat CreditAttribution: No Sssweat commentedIn the meantime, until such feature gets added to core, you can use the Select 2 module, here is an article about it. Make sure you read its READ.me to learn how to use.
Comment #17
ckrinaClosing as a duplicate of #3222995: Implement chips based autocomplete designs.