You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The primary piece of functionality in Content Libraries V2 is to enable authors to create component xblocks in the Library and then add those components to one or multiple courses. Additional info is here.
It only works in development mode (i.e, tutor dev)
It has not been updated for Olive (i.e., Tutor 15.0.0)
Acceptance Criteria
A set of updated plugins that will enable interested providers to automatically configure blockstore and start running the Library Authoring MFE frontend in "alpha", so that they can test-drive the new Content Libraries v2 functionality.
OpenCraft created a demo of how the current Library Authoring plugin works and what users will be able to do once it's running - namely:
Interact with Content Libraries V2
Add new text, problems and video components to content libraries
Pull those components from content libraries into their courses in Studio via the "Library Sourced" button (requires configuration in Advanced Settings, "library_sourced")
The expectation is that a new or updated Library Authoring Tutor plugin, in conjunction with a new Blockstore plugin, will achieve parity in terms of enabling users to test the functionality, as described above.
In addition:
Blockstore plugin
Works as well with tutor local launch as with the legacy devstack
Works with block storage, and in particular, with the Tutor minio plugin
Works with S3
Works with Kubernetes
Library Authoring plugin
Works with the Blockstore plugin
Works with tutor local, and not just tutor dev
tutor plugins enable library_authoring_mfe turns the MFE on automatically - no further need for feature flag or waffle flag manual manipulation
The new editors should be enabled by default (depends on the course-authoring MFE)
Other considerations
Content Libraries V2 is not a finished product. The new editors are only partially complete. Thus, the expectation is not that we are presenting users with new, shiny functionality. Rather, we want to give power-users the ability to play around with the new functionality in an alpha environment, to provide early feedback, etc.
Open questions
What happens if you enable the Library Authoring MFE plugin, but not the Blockstore one?
Maybe some specific error message in the MFE's UI when Blockstore is not there
The text was updated successfully, but these errors were encountered:
The primary piece of functionality in Content Libraries V2 is to enable authors to create component xblocks in the Library and then add those components to one or multiple courses. Additional info is here.
This functionality is contingent on the Library Authoring MFE, which is not ready for a Named Release yet. As a workaround, OpenCraft created an unofficial Tutor plugin for the Library Authoring MFE, but:
tutor dev
)Acceptance Criteria
A set of updated plugins that will enable interested providers to automatically configure blockstore and start running the Library Authoring MFE frontend in "alpha", so that they can test-drive the new Content Libraries v2 functionality.
OpenCraft created a demo of how the current Library Authoring plugin works and what users will be able to do once it's running - namely:
The expectation is that a new or updated Library Authoring Tutor plugin, in conjunction with a new Blockstore plugin, will achieve parity in terms of enabling users to test the functionality, as described above.
In addition:
Blockstore plugin
tutor local launch
as with the legacy devstackLibrary Authoring plugin
tutor local
, and not justtutor dev
tutor plugins enable library_authoring_mfe
turns the MFE on automatically - no further need for feature flag or waffle flag manual manipulationOther considerations
Content Libraries V2 is not a finished product. The new editors are only partially complete. Thus, the expectation is not that we are presenting users with new, shiny functionality. Rather, we want to give power-users the ability to play around with the new functionality in an alpha environment, to provide early feedback, etc.
Open questions
The text was updated successfully, but these errors were encountered: