openedx / openedx/paragon

Proposal of a new area (banner area) on Card Component

Open
#2,997 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
140
Forks
100
Avg merge
1h 3m
Merged PRs (30d)
30

Description

Feedback summary

Improvements

In accordance with the decisions of the marketplace transformation and in order to use a component that reflects the new design of the Card component, we suggest making it possible to display an optional area at the top of the card.

Like a banner (e.g. <Card.BannerCap> or similar) so that we can show additional information about the card, such as the type of product (e.g. Certificate Program), "share" and "save for later" options or other components/text/links.

The idea is to standardize this area with regard to its positioning on the Card, making it possible to define the background color and content (like <Card.Section> where we can define its content).

As this banner can be optional, the Card's current design can still be used.

In the image below:
(left) current representation of the Card component
(right) template of the new Card component design with the banner area highlighted in red
image

Bugs

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a file, test, or entry point. Start by reviewing the existing Card component and the attached design reference, then clarify the banner API, supported content and background styling. Done should mean an optional top banner can be standardized without changing the current Card representation when it is omitted.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.