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

MFE Plugins: Create slots for the right and left sidebar spaces in the LMS #1526

Open
jmakowski1123 opened this issue Nov 18, 2024 · 2 comments
Assignees

Comments

@jmakowski1123
Copy link

jmakowski1123 commented Nov 18, 2024

"As a course administrator, I want to customize my learners' experience as they progress through course content, by customizing the space on either side of the course content."

In the Course Content pages of the LMS, there should be a plugin slot on the left side of the course content and the right side of the course content.

This is a barebones implementation to start, and both slots should be developed as default empty.

The slots should be configurable such that one or multiple plugins can be developed and implemented via the slots. For example, if users want to use the right sidebar space for three plugins - a notifications plugin, an upsell message, and an AI chat bot (just hypothetical examples) - they can implement all three on the sidebar and configure the order in which the plugins appear.

We will decide later on the core platform use of the slots. It is likely that the left sidebar slot will be used for sidebar navigation, and the right sidebar slot will be used for notifications, but TBD.

Image

@jmakowski1123
Copy link
Author

@brian-smith-tcril - Lmk if this makes sense and if it's in the correct rep.

@brian-smith-tcril
Copy link
Contributor

Overall this looks great! One small concern I have is with

both slots should be developed as default empty

I would think for an MVP we would want to have the slots wrap the existing sidebar components (including the existing ability for the sidebar components to show/hide themselves).

It is also quite likely @arbrandes has thoughts, and I am more than happy to add more technical context to this issue after discussing with him.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Being Developed
Development

No branches or pull requests

2 participants