openedx / openedx/paragon

[Tracker] Shared Design Collateral Paragon Enhancements

Open
#4,277 0 comments 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

Overview

This is a placeholder tracker issue connect with the Open edX Shared Design Collateral project: https://openedx.atlassian.net/wiki/spaces/BPL/pages/6164414467/Open+edX+Shared+Design+Collateral

It will be populated with links to some potential bugs and usability/design enhancement future-fixes identified as part of the initiative. This tracker exists to associate those issues as we open them, and to help organize them within a project board in the future.

Categories

Throughout the process of modernizing the Paragon Figma design library, we identified some key categories of design and usability issues, including:

  • Some a11y issues like contrast in default docsite configs or default component states
  • Some inconsistent token usage, especially for areas like font styles, padding, and border radii
  • Areas of the Figma file we updated to match the live React components, but where we recommend updating the codebase to align with the previous version of the Figma file to improve the look or feel
  • Missing or nonstandard icons
  • Gaps or opportunities to enhance Paragon's usability as a design system, especially meta-issues such as the current component status tracking system

Tracked and Related Issues

See Sub-Issues.

Resolved Issues

  • ...

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

Start with the linked Open edX Shared Design Collateral project and the issue's Sub-Issues. This tracker names categories and future fixes but does not identify a file, test, entry point, or single implementation task. A concrete sub-issue with defined scope and completion criteria is needed before work can be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
figma, javascript, react
Domain
accessibility, design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.