15 minutes | Paragon maintainership handoffs | @Adam Stankiewicz | 2U/edX is handing off maintainership to Axim more formally. Part of this includes ensuring the following handoff items are discussed. Notes: [Brian] Axim can use existing or new GitHub user [Brian] The main goal is to drive more community contribution to Paragon, with Brian taking on the responsibilities or leading that effort [Brian] PWG will remain, but we want more people to get involved in the design system Might be helpful to have a base theme Figma that Open edX consumers can leverage “Load a theme” instead of having a theme switcher in the future
Next steps: Brian working with Adolfo to find contributions, especially design tokens Gabe attend next Product Working Group
|
5 min
| List height in the Dropdown component | @Vladyslav Zadorozhnii
| [Playground] List height in Dropdown component · Issue #2988 · openedx/paragon [Gabe] Q: how is the default height of the Dropdown determined? Is it determined by maximum number of visible dropdown items? More nuanced, e.g. never taller than the viewport? [Vlad] Should this be responsive? E.g., 5 items for mobile-sized viewport; 10 items for desktop. Might be worth testing in mobile specifically.
[Brian] Screen width can be large while having a narrow height. Our breakpoints are width-only. [Adam] What about responsiveness based on the container the Dropdown is rendered in? Rendered container width !== always equal viewport responsiveness. [Brian] Are there existing use cases of Dropdown in platform today we could draw from as prior art? [Ben] semantic ui provides decent Dropdown examples to compare against our Bootstrap-based Dropdown. [Mahdiye] Are there alternative UI paradigms to consider here? Tenative decision: reduce number of items displayed in Dropdown based on responsiveness. Details TBD.
|