As we working towards a KDS v5.0.0, we need to finalize this version of the KCard API, which is flexible enough for known use cases across Kolibri and Studio. While we are already beginning to implement the new KCard in Coach, ensuring suitability/that it is fit for purpose in existing Learn use cases will help us keep the API stable (or at least not have to immediately change it due to an oversight, hopefully)
Overview
As we working towards a KDS v5.0.0, we need to finalize this version of the
KCardAPI, which is flexible enough for known use cases across Kolibri and Studio. While we are already beginning to implement the newKCardin Coach, ensuring suitability/that it is fit for purpose in existingLearnuse cases will help us keep the API stable (or at least not have to immediately change it due to an oversight, hopefully)[TO DO: Acceptance criteria]