2022-08-15 Meeting notes

Shared #paragon-working-group Slack channel between 2U/edX Slack and Open edX Slack.

Are there any guidelines we should have for what NOT to share in #paragon-working-group? Anything that can’t be shared publicly?

Notes

• X

• Do NOT share “company sensitive information”

  • What about projects (e.g., revenue)?

  • Is there a business / legal person we could get clarification what is considered “sensitive”?

• Internal and external channels in slack?

• How can we get quicker design answers in #paragon-working-group Slack?

• Decision:

  • We’ll stick to single shared #paragon-working-group channel for now and monitor activity for anything that shouldn’t be posted publicly.

Dropdown / header dark variant

Notes:

• Dark header? Dark variant for dropdown?

  • Why do we use a dark header in one place but no where else?

  • Was the dark variant of dropdown design reviewed? Since it’s not part of Paragon right now.

Notes continuation:

• Is a dark background header a common pattern we envision being used elsewhere?

  • How does that play into the Paragon’s Navbar component?

  • Most MFE headers are using a shared header component that doesn’t give much flexibility right now.

• In PWG, Ben’s squad will file a Github issue for implementation of Paragon’s dropdown dark variant.

  • Blocker: spec for dark variant of Dropdown needed.

• Can we bring this to PWG to discuss/review with larger group?

• Can we have a process spun up to do a PWG design review, more asynchronously?