2022-10-26 Meeting notes

10-15 minutes

Common SVG Illustrations

@Adam Stankiewicz

@Alena Egorova

• Should there be a common place to store frequently used illustrations? If so, where would it make sense to store them?

• Would we need to store several color options for each SVG?

• Are the illustrations edX.org specific or are they relevant to Open edX as well?

  • Likely edX.org specific due to colors, etc.

• [Alena] Are there any guidelines around when to use which SVG?

• Couldn’t get a license to redistribute which is why they are only in the design system Figma library

  • Could they be a separate NPM package?

  •  

• Is there a framework for illustrations?

  • Placeholder illustrations by theme.

• Figma

2 minutes

Deprecation of edX-bootstrap

@Jeff Witt

See https://edx-internal.slack.com/archives/C02BMP2RD5Y/p1666776944661039

• DEPR ticket for edx-bootstrap

  • Bunch of stuff is still using it

  • Figuring out its dependencies.

• We should compile a list of which repos use this edx-bootstrap repo.

• Jeremy Bowman already thinking through a potential solution.

•  

10 minutes

UX-focused gathering space

@Adolfo Brandes

• At a previous meeting @Gabriel Weinberg offered to ask around about when/where we could start getting the community involved in UX discussions

• I’ve (@Adolfo Brandes) been asked the same question, so I’m checking back

Notes:

• Community also happy to just stay informed on what’s happening with design work, rather than actively contributing.

• New FedX meeting is more technical in nature (FED), not so much design conversations.

• [Gabe] Is this improvements to contributions to Paragon specifically? Or is it more for feature development across the platform?

• 2U has largely driven design of Open edX, but tCRIL/community has desire to keep taps on design updates to these platforms.

• PWG is probably not the right group for this purpose since not all feature work comes through PWG (only when a use case for new/updated component, for example).

• FWG is also more technical in nature.

• We’re looking for a cross-functional meeting for context/knowledge sharing around design.

• Gabe + Adolfo to sync offline to find a better medium for these conversations.

• Ali would also like to get involved in this

  • May also do an inform about this with Product Working Group.

@Ali Hugo

• Best practices for adding/updating things to Paragon.

  • E.g., naming Figma layers, etc.

• Contribution process.

  • Contribution Process

• Reach out in weekly PWG meeting or async in #paragon-working-group Slack channel.

•