Demo of latest features
MFE
Library license configuration
User access configuration
Video-type libraries
Problem-type libraries
Filtering and pagination in the library list
Studio and LMS
Adding library content to a course
What happens when you update a library?
Block editor modernization
Braden’s latest comment: https://github.com/edx/edx-platform/pull/25125#issuecomment-702421440
“It's not just these two blocks unfortuntely; there are a number of (first and third party) XBlocks that make assumptions about the surrounding frontend runtime environment of the
studio_view. The "API" for how XBlocks render and usestudio_viewhas always been very fuzzy, and I'm pretty sure I've seen XBlocks rely on functionality like tabs in the studio edit dialog that depend on Studio's existing JS+CSS.”
Do we forsee a situation where many blocks' editors will simply not work in the MFE without modernization?
If so, do we need to rethink the Library Authoring MFE component editor?
(Adolfo replies prior to the meeting:) We can conduct a survey of which ones work, and which don’t. Just keep in mind that feature-parity-wise, legacy libraries to this day do not support advanced block types (while v2 will work with most), so the list of blocks to test is not as long as one would think.
UX feedback timeline
Marco Morales (Deactivated) - Can you speak to when the team will be able to see mocks?
How does that timeline affect the project?
Milestone 3 planning
M3 was originally the beginning of Taxonomies, Tagging.
We identified last time that we should instead focus on bringing M2 results to parity with V1 libraries. Does that still sound good?
Can we identify a high-level objective for this milestone?
$customHeader
Manage space
Manage content
Integrations