[later phase] Create components for a default design system

Thanks for making this happen, @bnjmnm! 🤩🚀

Common components
Text
Accordion
Tabs
Slider
Hero
Card
Columns/Grid

Some prior art for inspiration:

• UI Patterns →
• Bootstrap Paragraphs →

I'm sure there are a ton more.

Thanks @thejimbirch for mentioning UI Patterns.

I would enlarge the scope to the UI Suite ecosystem ( https://www.drupal.org/project/ui_suite → ), focusing on all full Design system implementations such as :
- https://www.drupal.org/project/ui_suite_bootstrap →
- https://www.drupal.org/project/ui_suite_dsfr →
- https://www.drupal.org/project/ui_suite_uswds →
- https://www.drupal.org/project/ui_suite_material →

All of these themes are UI Patterns 1 implementations. As UI Patterns 2 development (built on top of SDC) is in progress, we already started to convert automatically these UI Patterns components to SDC components :
- https://www.drupal.org/project/ui_suite_bootstrap/issues/3412076 📌 [5.1.x] Automatic conversion to SDC & UI Patterns 2.x Needs work
- https://www.drupal.org/project/ui_suite_uswds/issues/3412077 📌 Automatic conversion to SDC & UI Patterns 2.x Postponed
- https://www.drupal.org/project/ui_suite_dsfr/issues/3419042 📌 Automatic conversion to SDC & UI Patterns 2.x Postponed

Hope all of this could give some inspiration.

Another potential example to look at is the Carbon Design System, which is Open Source.

Is the intent to have a list of components we may want to support? Or are we looking for an actual set of components? If we are, we will likely need the design system for them (or we can extrapolate it if we are building the components for an existing theme like Olivero).

However, there is a chance that what we are looking for theme independent components. If that is the case, we might want to discuss first how to best implement those.

Also linking to https://bradfrost.com/blog/post/a-global-design-system/

IMHO, several ways could be explored :

• Build a design system based on Olivero (some components are already in SDC process)
• Build a flexible "Drupal" design system from scractch
• Implement open source full design systems (like UI Suite have done for several years, with today automatic conversion from UI Patterns componemts to SDC components)

In terms of Drupal large adoption, all these ways could lead to a drupal.org components library like Wordpress does --> https://wordpress.org/patterns/

... that could be available during Drupal installation ?

Let's dream :) !

Another useful resource: https://component.gallery/design-systems/

tim.plunkett → made their first commit to this issue’s fork.

This was erroring when rendering components. Updated the code to be slightly less buggy.

There's some great work on 📌 Introduce an example set of representative SDC components; transition from "component list" to "component tree" Fixed to draft few components to begin with.

Just a note on the components in 📌 Introduce an example set of representative SDC components; transition from "component list" to "component tree" Fixed . They are very much intended as a place to test and experiment with the config/data structures experience builder will need. They may serve as a good starting point for some of the default components but definitely are not meant to be included as defaults.

Wim Leers → closed merge request !1

See #3446722-13: Create an example set of SDC components → — I'll make sure to work on this in tandem with that.

Per #8, he's been presenting on this for awhile but here's a more recent one:

https://www.youtube.com/watch?v=1JFp6kH5dFo

Wim Leers → credited pdureau → .

Capturing @pdureau's concern WRT XB's current components/image/image.component.yml, posted at https://git.drupalcode.org/project/experience_builder/-/merge_requests/2... and at #3446722-29: Introduce an example set of representative SDC components; transition from "component list" to "component tree" → .

It's out of scope/irrelevant there, but here it becomes relevant. 👍

📌 Introduce an example set of representative SDC components; transition from "component list" to "component tree" Fixed is in. 3 of the components in that MR didn't land there, but were extracted to a follow-up: 📌 Follow-up for #3446722: `side_by_side` + `accordion` (+ maybe `text`) components Active .

I think it makes sense to keep this issue postponed until a later phase, at least until after 📌 Implement temporary design system for the DrupalCon Barcelona demo Needs work .