-
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
New component tile for "Library Content" in Add new component to unit workflow #1335
Comments
@sdaitzman @jmakowski1123 Do you have this icon available as an SVG ? I don't know where it came from. |
@sdaitzman @jmakowski1123 Also I need a second version of the icon to indicate when the link is broken/invalid. See kdmccormick/edx-platform#16 . |
@bradenmacdonald that's the newsstand icon from the Material Sharp icon set, SVG available here: https://fonts.google.com/icons?selected=Material+Symbols+Outlined:newsstand:FILL@0;wght@400;GRAD@0;opsz@24&icon.size=24 We don't currently have a broken/invalid link icon selected, but this link_off icon could be used: https://fonts.google.com/icons?selected=Material+Symbols+Outlined:link_off:FILL@0;wght@400;GRAD@0;opsz@24&icon.size=24&icon.color=%235f6368&icon.query=link |
Thanks @sdaitzman |
The new Libraries feature needs a brand new component tile/block called "Library Content" in the "Add new component" section of the Unit Page.
The icon for the new tile is:
The V1 library component tile, which is also called "Library Content", should be changed to be called "Legacy Library" instead.
Per the configuration requirements, it is possible for some instances to have both Legacy Libraries and the new Libraries feature on simultaneously. This will happen if an instance has manually configured V1 Libraries. In those cases, authors should see both the "Legacy Library" block and the "Content Library" block.
The new Library Content block/tile should have a "beta" label on it, so that authors can see very clearly that this block corresponds to the new Libraries feature set.
The text was updated successfully, but these errors were encountered: