- Issue created by @ckrina
- 🇪🇸Spain ckrina Barcelona
Note: I haven’t added as components the following items:
- Admin Toolbar. I see this more as a region rather than a component
- Top Bar. Same, I see this more as a a region
- Body Scroll lock: I see this more as an utility
I know @finnsky had ideas to plan Phase 2, so leaving this here so he can work on it.
- 🇦🇺Australia Jon Nunan
Break the JS into components: @todo a proposal of specific steps and issues
By "components" are we talking Web Component custom elements, or just breaking the functionality up by SDC component?
I'd be a fan of exploring the first option as it would also allow some style encapsulation. I've started playing around with writing my front end themes with more a CUBE CSS (https://cube.fyi/) approach, but I find that often leads to conflicts with admin elements, so having admin elements outside the frontend css with Shadow DOM could be a nice win.
- 🇷🇸Serbia finnsky
Thank you for your interest.
Specifically in this task we mean SDC Drupal components.
But of course we should keep in mind web components as a promising technology. Especially in the Navigation module because it should look the same in the context of any Drupal theme. (and any basic styles)
If you are interested in web components in the core, then I know two tasks where they can appear (sorry for the off-topic)
https://www.drupal.org/project/drupal/issues/3405822 📌 Use webcomponents for dropbutton Needs review
https://www.drupal.org/project/drupal/issues/3100083 📌 Add js message theme override to match Umami message markup Needs review