search

DukeLearningInnovation / kits

https://dukelearninginnovation.github.io/kits
GNU General Public License v3.0
37 stars 5 forks source link

Kits is different than building another LMS #32

Closed profmikegreene closed 4 years ago

profmikegreene commented 6 years ago

A traditional LMS is a collection of learning tools built together into a single product. This would be disaggregating those tools, selecting existing best-of-breeds among each tool use case, and skinning/linking/embedding them together in one place. Each tool could ideally be replaceable when necessary or desired, and the skin/shell could be replaced as well without losing any tools. The unity of the LMS made information transfer easy at the cost of having less than ideal tools and functions; the NGDLE would have the best available tools, at the cost of greater pressure on information transfer (I/O standards, APIs, LTI, QTI, etc...). From Justin

JustinJohnsen commented 6 years ago

It's object-oriented programming at the application ecosystem level (without the same strong standardization of I/O between objects).

profmikegreene commented 6 years ago

Something this project is that an LMS isn't and most likely cannot be is a technical specification for pedagogy - we aren't building announcement tools, but should build a spec for what an announcement is so that any tool that provides announcements can have those announcements sent to learn.duke and displayed in a uniform way to students. LTI doesn't come anywhere close to this. LRNWebComponents is much closer. This is not MVP1.