...
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) if search requirements become more advanced and / or if we need to account for ‘find and replace’ / ‘bulk replace’ functionality in the future
Confluence and Google Drive use a combined 'active filter / dropdown selection' element for their search filters. Investigate whether this is a more user-friendly approach than the separate filter and chips that are currently used in the design
We discussed an implementation issue that came up whilst building the ability to add internal links to course sections (see proposal)
Santiago on Slack: “During the implementation of the functionality to insert links to internal sections of the course graphically (Jump To), some unexpected changes arose. Initially, the proposed solution, which had product approval, was this which connected Jump To with URL insertion. However, during development, we realized that TinyMCE already offered the option to insert URLs. Therefore, we have decided to retain this native option and separate our Jump To plugin. We propose that the plugin be as shown in the attached images where the user selects a text and can insert a link to an internal section of the course. If the user does not select the text, a message appears indicating that they must do so.”
We discussed what the process should be for getting product approval on updates made post-approval. We decided that the situation should be described on the UX/UI Working Group Slack Channel, and that a simple
or objection would be enough to approve/object to the updated proposal