- Issue created by @lauriii
- Assigned to lauriii
- 🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
What is this postponed on? On design? On an outcome of the discussion at 📌 Clarify "components" vs "elements" vs "patterns" Active ?
This affects 🌱 [META] Configuration management: define needed config entity types Active and would be one of the logical next things to work on now that ✨ Allow specifying default props values when opting an SDC in for XB Fixed landed.
- 🇫🇮Finland lauriii Finland
I'm working with a UX designers and a researcher to define this. We have formed a hypothesis and we're planning to start testing on Monday.
- 🇫🇮Finland lauriii Finland
We are planning to launch a research utilizing unmoderated interviews + tree testing next Monday.
Objectives
- Define what building blocks are most important to the potential users of the Experience Builder (XB).
- Define the ideal menu IA for users to efficiently navigate the tool.
- Understand the limits designs systems are pushed to out in the marketplace and the ideal arrangement for users. (prioritizing mid-market level users, including enterprise data to keep designs scalable for their needs as well.
Users/Participants
We can target the following groups on PlaybookUX:
Personas
- Designers (Maggie & Amir)
- Front-end developers (Clare & Keith)
Target Markets
- Education/schools & Volunteer orgs (primary)
- Mid-market agencies (primary)
- Enterprise users
- 🇫🇮Finland lauriii Finland
Adding a link to Figma which has a benchmark + a hypothesis to test: https://www.figma.com/board/PtSgs0OuOaU1uwpstivpmM/Benchmark?node-id=0-1....
- 🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
This came up in a meeting with @larowlan — see the parenthetical at the bottom of #3454519-22: [META] Support component types other than SDC → , quoted here for simplicity:
(For example, we also discussed the need for per-slot restrictions on which components would be allowed, which is possible in Layout Builder using https://www.drupal.org/project/layout_builder_restrictions → , but that module has scalability issues — through no fault of its own — because the "tags" are not built in, resulting in hundreds of lines of YAML in
third_party_settings
😳. That validates @lauriii's thinking to make that an inherent part — see #21.4. Related: 📌 [needs design] Define built-in components and categorization for components Postponed .)Lee confirms the need for this based on real-world experience with Layout Builder 👍
- 🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
Matching the issue title prefix pattern I used for 📌 Clarify "components" vs "elements" vs "patterns" Active .