2025-04-02 Meeting notes

@Brian Smith

• Last chance for people to take a look at fix: create the brand fallback for {} PARAGON_THEME_URLS by dcoa · Pull Request #785 · openedx/frontend-platform before I merge it

@Brian Smith

• Open question, thoughts on how to get the styles for both the Paragon docs site and MFEs using the same build configs to avoid discrepancies?

• [Adam] Can we pull frontend-build configs in in some way when deploying the docs site?

  • [Brian] Maybe break config into parts that can be used by both webpack vs gatsby configs?

• Next steps:

  • @Brian Smith to make an issue for it

  • Add discovery about shared config stuff to issue

@Brian Smith

• frontend-app-publisher has footer-edx in the package.json feat: design tokens support by dcoa · Pull Request #1003 · openedx/frontend-app-publisher

• Next steps:

  • @Adam Stankiewicz will push to get the 2U deploy scripts updated to handle the aliasing without relying on it happening in the upstream package.json

@Adam Stankiewicz

Migrating to 2U’s @edx/elm-theme, regarding Alert (and possibly other components):

Open edX theme

Open

Elm theme

Open

Challenges:

• By default, most MFEs rely on default <Button> variant (i.e., primary) in the Alert as depicted in the current Paragon Figma.

• However, in the Figma document for 2U’s Elm Theme, the Alert CTAs are using the brand variant.

• How might 2U (and other instances) mitigate which button variant is used within Alert components if openedx MFEs continue to use primary variant? If we change the upstream openedx MFEs to switch to brand variant, it’ll change the designs for the community, too.

Raised by @Max Frank.

Next steps:

• @Adam Stankiewicz and @Max Frank to draft an ADR for variant/other style overrides as part of env.config.jsx - will bring to Frontend WG next week