2022-11-2 Meeting notes

5 minutes

Slack channel owner change

@Gabriel Weinberg

• Need a shepherd to see through a migration of ownership to 2U from edX.

• Update workflow reminder once that is complete

• Any other steps we should take? Open edX connection?

• Open questions:

  • How does the new ownership work with multiple connections

  • Should Open edX be the owner of the channel or 2U?

  • Still looking for an owner for this.

    • If interested, ping #paragon-working-group

15-20 minutes

Search bar in DataTable

@Kira Miller

• Why do we have to have different filters or search bars to search different things?

• Can we look into creating a main search that looks through all columns?

• Notes:

  • Filter APIs | TanStack Table Docs can be used

  • disableFilters

    disableGlobalFilter

• Some prior art / thinking around treating filters/search as a distinct subcomponent:

  • https://www.figma.com/file/eGmDp94FlqEr4iSqy1Uc1K/Paragon-Design-System?node-id=17393%3A55979

  • Could be used within DataTable or elsewhere.

10-15 minutes

Form.Autosuggest

@Brian Smith

@Adam Stankiewicz

https://paragon-openedx.netlify.app/components/form/form-autosuggest/

“when handling the error state, it's not quite clear what the intended behavior is”

“if you click into a control and immediately click/tab out, you will get the "Error, no selected value" text”

“however, if text is entered and then deleted there is no error message”

“there is also no error message if text is entered that doesn't match anything in the dropdown (for example, typing "foo" in any of the sample boxes)”

Questions:

1. What is the intended behavior for the error state?

   1. The Figma specs (here and here) define what the error state should look like, but doesn’t really define when the error should appear.

2. Free text or should it only support selection from limited list of items in the dropdown (configurable).

3. “Feels like the component isn't fully defined”

Notes:

• `Form.Autosuggest` error states and freeform text · Issue #1732 · openedx/paragon

• When is it in error state. Needs figma spec.

• Refer to Mature Autocomplete library for understanding edge cases of behavior (e.g., material).

• [A11y] A form field with nothing in it is not an error, but yes on blur.

• Ideally configure to allow or not allow freeform text as an option

15 minutes

Docsite navbar

@Kavya Basu

https://paragon-openedx.netlify.app/components/navbar/#home

• Review of docsite navigation redesign. (This ticket)

Notes:

• configure sheet to be able to cllick outside to close

•  

15 minutes

Questions about the contribution process

@Ali Hugo

• What’s the best async way to ask for help, feedback, or confirmation when working on a component in Figma? (adding a comment in Figma / Github / Slack?)

  • Slack channel (#paragon-working-group) or in the PWG meeting.

  • Figma

• Where can I find the “proposal states” mentioned in the Contribution process document? (e.g. draft, ready for review, approved to add etc). 

  • We’ve moved away from Jira for Github Issues, but the statuses haven’t really been defined there.

  • There are some design related labels on the board here.

  • This is a known gap in our documentation.

• How should I indicate that I’ve made an addition or change to an existing component in Figma (e.g. I added a skeleton version of the Card and DataTable)

  • Presenting in the PWG meeting.

  • Use a different section in the Figma (v1 → v2 → v3, etc.)

  • Inform #paragon-working-group.

  • If it's an update to an existing component or a new component, bring for early discussion before design/implementation work begins for early feedback / decision making.

• Is there an accepted standard for how to name Figma layers?

• What level of perfection is required in Figma? Sometimes I can’t get a component to respond perfectly when I resize it in Figma!