-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Add from Library buttons (Authoring MFE - Unit Page) #1462
Comments
@jmakowski1123 @sdaitzman FYI - please review this new ticket. |
cc @GlugovGrGlib for visibility. These are small additions being made to the new unit page MFE. |
@bradenmacdonald We'd also like to introduce a new auto order to the component block tiles. See below. Could that be part of this story, or should be a separate story? Text |
@jmakowski1123 What do you mean by "auto order"? If it's just a new order that's fixed, we can include the change in this story. But if you mean something more dynamic, let's make a separate story. |
I just mean a new order that's fixed. That order should be: (based on logic of which blocks are most commonly used and which blocks are closely related) Text |
@jmakowski1123 @lizc577 @sdaitzman @marcotuts This is ready for AC testing on the sandbox |
Update the various buttons for adding library content to a unit, in the authoring MFE.
Currently it looks like this:
But it should be more like the legacy unit page:
Changes:
a. Make sure it works (it adds an
itembank
component). Currently, nothing happens when it's clicked.b. Ensure it is only visible if v2 libraries are enabled.
c. Use the correct icon (Paragon's
casino
icon)d. Add the "beta" label
a. Make sure it works (display a modal to choose multiple items, add them to the course with
upstream_ref
set - see legacy UI behavior and copy that)b. Ensure it is only visible if v2 libraries are enabled.
c. Use the correct icon (newsstand - may need to add to Paragon)
d. Add the "beta" label
a. Ensure it is hidden if v1 libraries are disabled.
Note: 2a is potentially quite a large item so I suggest doing it in its own PR, separate from the other changes. However, don't spend a ton of time on it, as we'll be overhauling the entire workflow in Epic 7.
Note 2: we are not changing the color of the buttons.
The text was updated successfully, but these errors were encountered: