Page Comparison

The proposal is just an idea. Discussions on the draft serve to gather feedback and help prepare the idea to be

The proposal is ready for a review when it has: A succinct use case and purpose, a general description of behavior or variants, and a design reflected in at least a wireframe level fidelity.

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.

The group will consider the following:

• Review the use case from the

  Status
  colour Red title UX

  and

  Status
  colour Yellow title A11Y

  perspectives and come to an understanding of the need.

• Should this component live in Paragon?

• Determine if the use case is unique. If so, it should remain be a one-off solution.

• Do we agree on what to name this component?

Reviews move the proposal to

An accepted proposal is ready for further design and engineering work. A proposal is accepted with three approvals (minus the proposer), one from each UX, UI, A11y, and Eng. Once accepted the proposer should begin building out the component spec with UX/UI/Eng/A11y (if they have not already).

A deferred proposal should be designed and built as a one-off where it is needed. Move the proposal to a new folder in this space (TODO: when this happens the first time add a folder in the wiki in an appropriate location)

A proposal needs changes to become