Course Outline: Add Sidebar basics (`Add` button Flow)

[ChrisChV]

Design

Figma link

Add New	Add Existing

In the Scope

• Click on the Add button of the Header (Course Outline: Header Update #2622) opens the Add Sidebar.
• Click on the Add button of the Navbar (Course Outline: Info Sidebar & Navbar - Basics #2623) opens the Add Sidebar.
• The add sidebar should default open to the Add New tab
  • Add New tab shows a list: Section, Subsection, Unit
• In the Add Existing tab:
  • Reuse select from library modal. Show all containers of all libraries.
  • Reuse the same filters.
  • Add the filter by item type
  • Show all types of containers.
• when added in any tab, add the object to the last possible location in the course with the newly added content selected and sidebar open.
  • Because content cannot be added to library referenced object, the selected content should add to the last possible location (ie: if adding a subsection but the last section is a library referenced section, add to the section above). [to confirm]
  • in the case where there are no possible places to add, [Need to determine
• Cards should have default Paragon hover states

Out of Scope

• Library filter
• Filter by Collection
• Preview

[edschema]

Hi @ChrisChV, Subsections and units should also be in scope. This is a screen of the outline with all hover actions are shown. In the design, the intent is for the add buttons to be hidden unless a user mouses over the spaces.:

[ChrisChV]

Hi @edschema

Subsections and units should also be in scope. This is a screen of the outline with all hover actions are shown. In the design, the intent is for the add buttons to be hidden unless a user mouses over the spaces.:

Yes, I've placed that case in flow A, using the buttons: #2631

This issue (Flow B) is when the user clicks on the Add button in the header and uses the Select Location Step. Since the select location step is only for sections, I have limited this flow B to sections for now.

[bradenmacdonald]

@ChrisChV As I understand it, we don't need both. If we implement the "hover to add", then that will cover most use cases. If there is also an "Add" button in the header, I think it would be fine to just have it append a new section to the end, rather than building out yet another way of selecting where to put it. But if we don't end up building the "hover to add" then we'll need something else like the "Select Location Step". I may be wrong though :)

[edschema]

This add flow should be much simpler than originally designed. Behavior is as below:

• sidebar opens from opening the 'add' sidebar from the page level actions
• sidebar has two tabs: "add new" and "add existing"
• all component types are shown
• when added, components are added to the last possible location
  • section added to the end of a course
  • subsection added to the end of the last section in a course
  • unit added to the end of the last subsection in a course.

TBD:

• if the sidebar is open and a user clicks one of the add existing buttons from within the course outline, we may want to still have the placeholder described in Course Outline: Container Card Placeholder - Drag (Add Sidebar Flow A) #2632. Will confirm this soon.

[ChrisChV]

@edschema Thanks!

sidebar opens from opening the 'add' sidebar from the page level actions

Sorry, I'm still not clear on which button starts this flow. What do you mean by page level actions?

[edschema]

Hi @ChrisChV! The page level actions are the actions at the top of the page to the right of the page title:

[ChrisChV]

@edschema Thanks!