Resource discovery: Implement resource card

[MisRob]

Blocked by

• New component: Initial implementation of KCard component kolibri-design-system#625 (however, since the PR is nearly ready, can be developed in parallel locally via Running Kolibri with local Kolibri Design System)

Summary

In support of coach resource discovery we need to implement a new resource card. This will be one of the first cards in Kolibri built on top of KCard.

The final card is expected to look like:

It needs to show

• Resource title
• Resource description
• Metadata
• Resource thumbnail picture
• Resource thumbnail placeholder when picture is not available. The placeholder icon corresponds to learning activity type of the resource.
• Bookmark button icon (only emits event on click)
• Info button (only emits event on click)

References

• Resource discovery designs (see resource cards)
• Card specs designs
• Coach Resource Discovery #11888
• Sibling cards: Resource discovery: Implement channel card #12317, Resource discovery: Implement folder card #12318

Guidance

• Create a completely new component <AccessibleResourceCard> and use <KCard> at its basis
• Regarding the structure of production data that the card should display, examine existing resource cards in the Library and also see useSearch composable. In the scope of this issue, assume that data for the new card will have the same structure.
• For the purpose of development and review, display the new card at any place in Kolibri and remove the preview shortly before the final merge. It may be handy to work on the Library page because it has access to all data.
• Even though any of the existing cards shouldn’t be changed, they may contain some useful pieces of code for the new card so it’s recommended to examine them (see ResourceCard.vue when contentNode.is_leaf is truthy, LearningActivityIcon.vue, LearningActivityLabel.vue, ...)
• It is possible that KCard will need further updates to support all Kolibri cards. If there’s something that KCard doesn’t support yet, discuss with relevant people and determine next steps.

Out of scope

• Anything grid related (this includes card’s min and max width which will be grid’s responsibility, as well as checkboxes)
• Refactoring existing card components in Kolibri
• Implementing other parts of the coach resource discovery such as the side panel where cards will be displayed
• ‘Bookmark’ and ‘info’ fully functioning

Acceptance criteria

• The card is built on top of the KCard and contains elements listed above
• It supports all possible modes (e.g. for all various learning activities that a resource can have)
• It follows the designs closely (or discrepancies get discussed)
• It content tolerant (renders well for short strings, long strings, missing information, missing thumbnail picture, etc.)
• It is responsive
• It supports RTL (note that KCard will be responsible for basic layout RTL support, but some additional tweaks may be needed for content that is provided to it via slots etc.)
• It is ready to receive production data, meaning it doesn’t use hardcoded data inside the card but rather receives data from outside like it would in the final feature, for example in the form of an object passed via prop (or any other relevant manner)
• For the purpose of preview and QA, please include at least a couple of <AccessibleResourceCard>'s in <ul> and feed them with data that have same structure as production data and enough variance (see content tolerance criteria). Demonstrate all learning activities.
• If some components used in the current cards are re-used in this new card and tweaked for the purpose, there are no regressions in the old cards