Originally submitted on Github with significant input from Andrew MacPherson and Zoltan Horvath
Problem/Motivation
Recent interviews and research exposed pain points around Drupal's admin experience of looking and feeling dated, especially compared to our competitors, and universally cited that choosing a more modern-looking admin theme instantly led to Drupal being better-perceived by said users. There was an amazing community effort to Create a Style Guide For Seven that vastly improved its look + feel compared to the original, but Design best practices and Drupal functionality have moved on since then.
Proposed resolution
Implement new radios styles to create a favorable first impression of Drupal for evaluators and a better user experience for site authors. No functional differences.
Specification
Quick overview
This image is just a quick overview for radio specs. Please use the Figma link to full specification as the main resource for specs.

Full specification
FIGMA: https://www.figma.com/file/OqWgzAluHtsOd5uwm1lubFeH/Design-system?node-i...
This link is anchored to the board with the full specification. As an anonymous user you can see the design, but to actually be able to pick colors and sizes please login on Figma.
General specs:
Color palette
Remaining tasks
- Update patch styling to include time inputs
- Accessibility review
- RTL review (Right to left)
User interface changes
Allradios will be changed, no functional differences.
Test Pages
Places which has the checkbox visible: (TO VALIDATE)
- Drupal's main install form
- Bulk Edit Forms (eg. Content, Comments, Users etc.)
- Content Create Forms (eg. Add Content -> Article)
- Form Display (eg. Content Type -> Manage form display)
- Theme settings forms
- Permissions Forms
- Modules Page
- Views
- Administration Pages (eg. A modules admin page)
- /node/add/article (open vertical tab COMMENT SETTINGS)
- /admin/config/people/accounts
- /user/1/edit?destination=/admin/people
- /admin/people/create
| Comment | File | Size | Author |
|---|---|---|---|
| #37 | interdiff-3023256-33-37.txt | 2.2 KB | huzooka |
| #37 | claro-checkbox_radio_styles-3023256-37.patch | 35.25 KB | huzooka |
| #33 | interdiff-3023256-27-33.txt | 1.5 KB | huzooka |
| #33 | claro-checkbox_radio_styles-3023256-33.patch | 35.46 KB | huzooka |
| #27 | interdiff-3023256-24-27.txt | 302 bytes | huzooka |
Comments
Comment #2
antonellasev commentedComment #3
antonellasev commentedComment #4
antonellasev commentedComment #5
antonellasev commentedComment #6
antonellasevero commentedComment #7
huzookaComment #8
huzookaThis patch represents the stale state from the github PR #63.
Comment #9
huzookaI have to find/create a feature request against core for the Drupal.theme.checkbox function and research why Media library needs a non-standard checkbox for its select-all feature.
Comment #11
huzookaReasonable style cs fixes.
Comment #14
huzookaComment #16
huzookaComment #18
huzookaReady for review
Comment #20
saschaeggi@huzooka let me know if there is any problem with the design you might run into. cheers
Comment #21
lauriiiWe should create an issue to add this function into Drupal core, and to change the implementation to use this. We should also add a @todo with a link for that issue for all of these files to remember that we should change these once the theme function has been added to core.
We shouldn't use ids for theming since it is not reliable (ids are uniquified so they might change depending on the context).
Comment #22
huzooka@Lauriii
Issue #3024975: Add Drupal JavaScript theme function for checkbox created and referenced to code. I just added a detailed follow-up #3024996: Remove tableselect.js and media_library.view.js overrides as well.
Nice catch, I can't really see how I added those back.
Comment #23
huzookaForgot to add the patch.
Comment #24
huzookaComment #25
huzookaComment #27
huzookaAccidentally touched the unused
css/components/form.cssfile.Comment #29
huzookaComment #30
lauriiiWe could use a simpler syntax to define the theme function:
Thanks for opening the follow-up!
Comment #31
lauriiiComment #32
huzookaComment #33
huzookaComment #35
Kami Amiga commentedThose properties are the same as the ones at line 84. Couldn't the two selectors groups be merged ?
Is it wanted to use both px and rem values too ?
Same question as for the line 90.
Comment #36
huzookaComment #37
huzookaAddressing all of #35.
Comment #40
lauriiiLooks good! Thank you everyone!
Comment #42
lauriiiUpdated credits
Comment #44
lauriii