-
Notifications
You must be signed in to change notification settings - Fork 178
Open
Milestone
Description
Design
| Section | Subsection | Unit |
|---|---|---|
![]() |
![]() |
![]() |
In Scope
- Depends of the implementation of the add sidebar basics in Course Outline: Add Sidebar basics (
Addbutton Flow) #2629 - Open the add sidebar when clicking the
new ...oruse ... from librarybuttons already implemented in the course outline
- Depending on which add button is clicked, the sidebar renders differently:
User clicks an Add New button on the course outline:
- A new block should be created immediately for the type clicked (ie: "+ Add Subsection" creates a new Subsection)
- The block should be selected on the course outline with the info sidebar open
User clicks an Add Existing button on course outline:
| Section | Subsection | Unit | |
|---|---|---|---|
| Header | ![]() |
![]() |
![]() |
| Results | only sections | only subsection | only units |
- Once added, the sidebar for the added component should be opened and selected in the course outline
- If a user clicks the Add New tab after selecting add existing, the sidebar should render ONLY the relevant component type (ie: if the user clicked "Use Subsection from Library", and then clicked the add new tab from the sidebar, the only card listed should be the subsection card)
To Confirm: Remove nesting (back arrow) in header from add sidebars
No in the scope
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
In grooming





