Course Outline: Course/Section/Subsection In Context Sidebar

[ChrisChV]

In Scope

• This sidebar should reuse the content from the in-context analytics feature: https://docs.openedx.org/en/latest/community/release_notes/teak/aspects_updates.html
• Open this sidebar when the user click on the In Context button

[edschema]

@ChrisChV this sidebar should reuse the content from the in-context analytics feature: https://docs.openedx.org/en/latest/community/release_notes/teak/aspects_updates.html

[rpenido]

Hi @edschema!

Currently, Aspects is not part of the platform's core features.
Just to confirm: with this change, we are making Aspects part of the platform and adding the features that are possible today only via plugins (i.e., the in-context reports) to the frontend, right? CC @ChrisChV

[rpenido]

Hi @edschema!

Currently, Aspects is not part of the platform's core features. Just to confirm: with this change, we are making Aspects part of the platform and adding the features that are possible today only via plugins (i.e., the in-context reports) to the frontend, right? CC @ChrisChV

Hi @edschema! Could you confirm this?
An alternative would be to update the current openedx/frontend-plugin-aspects to work with the new design. CC @bradenmacdonald

[bradenmacdonald]

@rpenido It's probably worth asking on Slack on #wg-product-core and/or #content-libraries-relaunch-ux.

My best guess is this: we should not assume aspects is available, so the code should work either way. If aspects is available, we can display the in-context analytics etc. This can be implemented as a plugin or not, but it's probably best to implement it as a plugin. It should be enabled by default, but should also gracefully handle the situation where the plugin is enabled but Aspects is not installed/available, and just display "no analytics available" or something like that.

[edschema]

Note: need to add designs for the cases where an object does not have analytics.