\uD83D\uDDD3 Date
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
10 mins | Quick updates on current projects |
| |
25 mins | Open edX Figma Library - Next steps | Questions about next steps - conversation to kick off
| |
15 mins | Studio Search - Call for review | Taking the group through the latest designs for the Studio Search and asking for feedback | |
5 mins | Community Figma account | 1 person from each organization to fill out this Google Form with the email addresses of everyone in their organization who needs access to the Community Figma account |
🗒️ Meeting notes
Jenna would like to be involved in the user testing for the HMX Custom Pathways project that Cassie Zamparini is running
We discussed the best approach for the community Figma account. We decided it makes sense for Axim to be the account owner, but there are a number of considerations to take into account:
Axim would need to pay for / maintain any editor licenses
Hosting the edX and Open edX themes of the Paragon Design Library on different Figma accounts
Sharing and syncing of libraries across different accounts (is it possible?)
Required permissions for library use (can anyone invited as a viewer —even outside of the org— view but not use a library?
Investigate “branching” in Figma
A separate meeting will be set up between Axim and 2U to determine the best way forward
Ali Hugo ran the group through a prototype of the latest designs for the Studio Search project (part of the Content Tagging initiative. Some feedback from the group:
We discussed whether the “text”, “video”, and “problem” filters were sufficient to cover the various component types. We decided they were for now, as they account for 86% of the block types
We may need to add a dedicated search page (like in Confluence) in the future if search requirements become more advanced
✅ Action items
Ali Hugo to confirm whether the folder icon is in Paragon, and if not, whether we need to use an alternative