UX: Add other widgets than select

Created on 9 February 2022, over 2 years ago
Updated 17 April 2024, 2 months ago

Problem/Motivation

Often in design systems, it is possible to set multiple classes on one item and those classes are not exclusive. Example: a class to align the class, another one to put it in bold, another one to underline.

But currently as it is only possible to select one item per style, those classes needs to be declared in multiple styles which blotters the UI and add difficulty for the site builder to clearly see what is needed.

Proposed resolution

Be able to select multiple classes by either a multiple select or changing into checkboxes.

✨ Feature request
Status

Active

Version

1.0

Component

User interface

Created by

🇫🇷France Grimreaper France 🇫🇷

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇫🇷France pdureau Paris
    1. Add StyleType plugin type
    2. Add mechanism to guess default types
    3. Add StyleWidget plugin type
    4. Add Widgets plugins: Select, Radio, Checkbox, Number, ColorSelect & Toolbar
  • 🇮🇳India Sharique

    New widgets will be really helpful.
    With new widget options, there is an overlay with layout options in certain scenarios, for example in case of layout paragraphs, we can add same setting either using UI Styles or layout options.

  • 🇫🇷France pdureau Paris

    Hi Sharique, the widgets are only bringing improved UX for existing styling features.
    Styles are still list of mutually exclusive options. Each option is still a CSS class.

    We are not introducing other data types like booleans, integers...
    So, if there is an overlap with Layout Options, it must be already the case. Do yo usee it?

  • 🇮🇳India Sharique

    I see overlap in case of layout paragraphs, because we are using extensively. And this is already in a way. Not sure about other scenarios.
    Anyway we can revisit this later.

  • First commit to issue fork.
  • Merge request !47Draft: Init Style Type plugins. → (Open) created by maboy
  • Assigned to maboy
  • 🇫🇷France maboy
  • @maboy Nice! Thrilled to use this. Does it make sense to review the status quo now?

  • 🇫🇷France pdureau Paris

    In ✨ Provide more options to drive the display of the UI style form Active vbouchet has proposed:

    Alter the default "-None-" option to another label (for example, for a plugin around "Borders", "No border" makes more sense from a contributor standpoint).

    Why not... Maybe a new property like this one from Form API:

    #empty_option: (optional) The label to show for the first default option. By default, the label is automatically set to "- Select -" for a required field and "- None -" for an optional field.

    Let's credit him if we add this feature.

Production build 0.69.0 2024