As discussed in a couple of other places, let's consider transitioning the LMS module to Single-Directory Components (SDC) plus full compatibility with UI Suite, to modernize and simplify all front-end development. This will prevent the need for the LMS module to have to provide any theming of its own, while exposing components, props, and slots to front-end designers to easily manage the look & feel of all of the LMS components.
In practical terms, this would mean transitioning the existing /templates, /css, and /js into a single /components directory, plus updating any code references to them. Then we can also add any other components that would be helpful for the styling of courses, lessons, activities, navigation, progress tracking, messaging, etc.
The current components that need to be adapted include:
Let me know if we're in agreement on this, or if it needs further discussion. If we have a consensus, I propose to create a child issue to move existing components to SDC, and then add separate child issues as needed for full UI Suite compatibility.
Comments
Comment #2
graber commentedComment #3
ob3ron commentedAs discussed in a couple of other places, let's consider transitioning the LMS module to Single-Directory Components (SDC) plus full compatibility with UI Suite, to modernize and simplify all front-end development. This will prevent the need for the LMS module to have to provide any theming of its own, while exposing components, props, and slots to front-end designers to easily manage the look & feel of all of the LMS components.
In practical terms, this would mean transitioning the existing
/templates,/css, and/jsinto a single/componentsdirectory, plus updating any code references to them. Then we can also add any other components that would be helpful for the styling of courses, lessons, activities, navigation, progress tracking, messaging, etc.The current components that need to be adapted include:
Let me know if we're in agreement on this, or if it needs further discussion. If we have a consensus, I propose to create a child issue to move existing components to SDC, and then add separate child issues as needed for full UI Suite compatibility.
Comment #4
ob3ron commentedI've found a few other components that can be targeted for SDC conversion. Here's my suggested order of operations: