Full UI: ContentCardView [Blocked: #161]

[BenHenning]

In various locations, content cards will need to be displayed with rich-text. Android TextViews support rendering a subset HTML, though the default rich-text provided by the Oppia backend may need to be processed before simply being passed to the TextView. See the web rich-text component for specifics.

Mock: https://xd.adobe.com/spec/e2239cf4-9cde-4c08-5296-25316c1f0a14-9412/screen/40d6cf5f-f673-42c8-af15-035f711ef6b9/PM-IN-Introduction-

Checklist

• ContentCard (Left side)

• Learner Answer (Right side)

• Final touch up with padding, margin, animations and Accessibility Scanner test

[BenHenning]

This is blocked by #15 to retrieve exploration content data, but it can be designed & mostly built as soon as #4 is completed.

[BenHenning]

To simplify, this only needs to support basic HTML elements (li/b/etc.) + images.

[seanlip]

Note: links as well. (This includes links to other lessons within the app.)

[rt4914]

@veena14cs @nikitamarysolomanpvt Check the comments here.

[BenHenning]

After talking with @veena14cs over chat today, one consideration for implementation is: https://stackoverflow.com/a/36528149/3689782.

[BenHenning]

This is blocked on #161 for the card's initial structural implementation. Although no data controllers block this work, it should be fully tested with real Oppia HTML examples to avoid complicating downstream work items.

[veena14cs]

This is been fixed in PR #338 .