Skip to content
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

Add new/existing block interface for new units (high fidelity) #1607

Open
sdaitzman opened this issue Jan 24, 2025 · 6 comments
Open

Add new/existing block interface for new units (high fidelity) #1607

sdaitzman opened this issue Jan 24, 2025 · 6 comments
Assignees

Comments

@sdaitzman
Copy link

Image

Updated design pending:

https://www.figma.com/design/Y3gSyrpG6uncUUfjK7eQuo/Content-Libraries-v2.1-%5BOpen-edX%5D?node-id=6513-111551&t=gkJ4H82rBFHMP8Jb-11

@pomegranited
Copy link
Contributor

Hi @sdaitzman :) What does the "+ Add content" button do in this context, when all the new/existing content buttons are in the main page area?

@sdaitzman
Copy link
Author

Hi @pomegranited!! The new/existing content buttons in the main page area in this ticket are a shortcut that will only appear in empty units, to help users get started authoring the unit. The "+ Add content" button still always opens the Add Content sidebar. Basically, instead of an empty state, we're including a direct shortcut to add a first block.

Once there is ≥1 component inside the unit, that inline shortcut goes away, and users use the Add Content button in the top right, or Add new / Add existing shortcuts underneath the components. Both open the Add Sidebar to the corresponding state.

These workflows are a bit redundant, in the interest of making it very straightforward for users to add content to a unit. If we want to cut more scope from #1594, we could drop some of these options, or reuse the same Add New / Add Existing main view for empty units. Let me know if it would be helpful to mock that up?

Image

@sdaitzman
Copy link
Author

For Teak, based on Libraries product discussion with @jmakowski1123 today, if it helps to reduce scope: can largely just drop-in existing new content object from course authoring, and allow the new incremental Add sidebar "Existing Components" button to handle library component reuse in new units.

@pomegranited
Copy link
Contributor

@sdaitzman @bradenmacdonald @jmakowski1123 It looks like this task was excluded from Libraries 12 for Teak? It was moved down to "Dropped for now" on our estimates sheet.

Instead of this task, we have #1620 + #1619

Is this correct?

@bradenmacdonald
Copy link
Contributor

@pomegranited Yes, I thought that we were dropping this story entirely; since it only affects the empty state and you can add from the sidebar.

Though perhaps it would also be very easy to put in the existing "course" version of the "add content" workflow as an alternative, which is how I interpret what @sdaitzman just said.

@sdaitzman
Copy link
Author

@pomegranited @bradenmacdonald I wasn't sure if this story was dropped or scaled down from the estimates; the suggestion I added was for a scaled-down version. Completely fine to defer this until after Teak, will move it to post-Teak for clarity.

@sdaitzman sdaitzman assigned sdaitzman and unassigned marcotuts Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: UX/UI To Dos
Development

No branches or pull requests

4 participants