\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
\uD83E\uDD45 Goals
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
🎉 New Core Contributor 🎉 | [inform]Viktor Rusakov is now a Core Contributor to Paragon and, more broadly, Open edX, with merge rights to all frontend repos. This means Raccoon Gang’s work in Paragon will no longer be blocked by Adam needing to do the final PR review and merge to It also means there is another reviewer/merger available to assist with OSPRs to Paragon. | ||
Design tokens update regarding CSS utility classes | [inform] We merged in the PR from Andrey at eduNext to add support for CSS variables rather than the HEX values in the generated CSS utility classes from the design tokens build. | ||
https://paragon-openedx.netlify.app/components/modal/alert-modal/#variants | |||
Paragon documentation site navigation re-design | [inform] We recently released a new re-design of the Paragon documentation site’s navigation. https://paragon-openedx.netlify.app/  | ||
| Is the design for | ||
Paragon sandbox/playground demo | At one of the previous meetings an idea came up for creating a Paragon Playground page that would allow engineers / designers to test how components are displayed and working together. We’ve done some investigation and tried to implement a sandbox page for Paragon with playroom package similar to how Polaris does it. Here’s a deploy preview link to play around. Looking for feedback on whether this would be useful to Paragon users! Notable disadvantage so far of using playroom is that it seems to be nearly impossible to customize the UI. (without forking the whole repository that is) | ||
Documenting the path to becoming a Core Contributor for Paragon | [discussion] It may make sense to more concretely define the path to becoming a Core Contributor in the Paragon space to continue growing the number of available reviewers/mergers of PRs.
|