For Paragon Working Group moderators

...

Discussing and Reviewing Component Proposals

...

...

...

Discussing a draft

Provide feedback to help move a proposal from

The proposal is ready for a review when it has:

• A succinct use case and purpose

• Similar components in edX or in the wild (links)

• At least a wireframe

• General description of behavior or variants

Reviewing a proposal

Proposal Reviews start in person in the Paragon Working Group meeting and continue on Slack if needed. To get on the meeting agenda make a post in the #paragon-working-group channel on Slack. Reviews can result in moving the proposal to

...

• Are we adhering to our design system Design System Principles ?

  • Embrace reuse and ditch the unnecessary.

  • Strive for universal accessibility.

  • Build open source and theme ready.

  • Act like an owner.

• Should this component live in Paragon?

  • Is this component a new component or a variant of another one?

  • Is the use case unique? Should it be a one-off solution?

• Do we agree on what to name this component?

• Should we adopt an existing package instead of building this ourselves?

• Do we have any helpful feedback to improve the component’s design?

  • Review the use case from an accessibility, UX, and UI perspective.