2024-01-24 Meeting notes

5 minutes

Checkboxes inside DataTable cards

@Brian Smith

• https://github.com/openedx/paragon/issues/2881#issuecomment-1904662416

10 minutes

Authn CountryField Autosuggest

@Brian Smith

https://github.com/openedx/frontend-app-authn/issues/1133

10 minutes

Design tokens release strategy

@Brian Smith

• Challenge with alpha today:

  • Maintenance burden: syncing master → alpha.

  • Difficult to consumers to consume with peer dependencies.

  • Open edX community members are already backporting design tokens alpha to previous Open edX named releases, which is a time consuming endeavor.

• Get alpha branch with tokens into a good/happy place and merged into master, with a breaking change (v23).

• Will maintain a version v22 with:

  • Security patches

  • Bug fixes.

  • Any case-by-case issues where consuming projects can’t upgrade.

• Optimistic goal: some support for tokens in some Tutor MFEs by Redwood; then all Tutor-supported MFEs by the following release.

• Q: Where do we draw the line on what we backport?

  • Probably can be case-by-case, but should be a good reason why consuming project(s) can’t upgrade.

    • Baseline example:

      • frontend-app-admin-portal uses deprecated Table component and the UI design will have to change according to DataTable. This requires design input that we haven’t been able to get resources on.

• 2U Marketplace concerns:

  • Is the right messaging “this is stable / usable for use today”.

  • Rebuilding prospectus (Gatsby site powering edx.org). May be using a new Paragon theme.

    • Might make sense to start with tokens support when developing that new theme, rather than developing on the old paradigm (SCSS).