4:20 UX feedback: 1) Add container 2) Toggle on [√] Global style 3) Dropdown [ Choose... ▾ ] 👉 You could simplify the interaction design of this by combining 2+3 into just 1 UI element/step. Simply rename the dropdown to [ Choose global style … ] and get rid of the toggle. ℹ Only advantage of separating toggle + style-selector: You could keep the style and temporarily toggle off, and then on again without needing to select the style again. Analogy in code: Commented CSS class which you outcomment again, instead of completely deleting the CSS class and retyping again later. 👍 Toggling but keeping the class is a big flexibility advantage indeed. Is this use case supported in GenerateBlocks? Then this UX is justified. 👉 Still improvable: Make the dropdown a combobox. When toggling on, focus is already in combobox, ready for typing and autocompletion and selecting with ENTER. 👉 As long as you want/have to stay with the dropdown-menu: There's still one possible improvement: As there are possibly anyhow only few classes per block-element-type, maybe the better design is to just preselect the last used one. Then in many cases you are done already. If you want something else then you need to click. Which in the current UX you need to do each time (cumbersome!).
7:45 Create first h2 in page, select, turn on global style, select global style ; Go to next container, create second h2, select, turn on global style, select global style … → Many repetitive steps! 👉 Is it possible to simply copy the first h2 with the already assigned style, and then paste it into the second and third block each, and this pastes an h2 with the global style assigned? That would be my preferred workflow.
Wow that's impressive. I can already tell once I get used to this it's gonna be painful to not have this available across any non-GB blocks :(
4:20 UX feedback: 1) Add container 2) Toggle on [√] Global style 3) Dropdown [ Choose... ▾ ] 👉 You could simplify the interaction design of this by combining 2+3 into just 1 UI element/step. Simply rename the dropdown to [ Choose global style … ] and get rid of the toggle.
ℹ Only advantage of separating toggle + style-selector: You could keep the style and temporarily toggle off, and then on again without needing to select the style again. Analogy in code: Commented CSS class which you outcomment again, instead of completely deleting the CSS class and retyping again later.
👍 Toggling but keeping the class is a big flexibility advantage indeed. Is this use case supported in GenerateBlocks? Then this UX is justified.
👉 Still improvable: Make the dropdown a combobox. When toggling on, focus is already in combobox, ready for typing and autocompletion and selecting with ENTER.
👉 As long as you want/have to stay with the dropdown-menu: There's still one possible improvement: As there are possibly anyhow only few classes per block-element-type, maybe the better design is to just preselect the last used one. Then in many cases you are done already. If you want something else then you need to click. Which in the current UX you need to do each time (cumbersome!).
7:45 Create first h2 in page, select, turn on global style, select global style ; Go to next container, create second h2, select, turn on global style, select global style … → Many repetitive steps!
👉 Is it possible to simply copy the first h2 with the already assigned style, and then paste it into the second and third block each, and this pastes an h2 with the global style assigned? That would be my preferred workflow.
This would be useful for buttons.