2025-02-19 Meeting notes

All public Working Group meetings follow the Recording Policy for Open edX Meetings

\uD83D\uDDD3 Date

19 Feb 2025

Time

Item

Presenter

Notes

Adam Stankiewicz

Notes

findDOMNode is used by react-bootstrap’s OverlayTrigger
We are on Bootstrap 4 and react-bootstrap v1.
Open edX has not yet decided what to do with Bootstrap v4 → v5 (or move away from Bootstrap)
- Caveat with the v5 upgrade: with design tokens / CSS variables, we’d need to continue porting some v5 Bootstrap code locally within Paragon.
Next steps: Bring this discussion to FWG for broader discussion & possibly involve UI/UX WG, too (as needed).

Just want to go through the open comments to see if we can move some of the conversations forward

@edx/brand-edx.org is hardcoded in edx-platform’s package.json.
- Why? 2U’s build pipeline for edx-platform doesn’t properly handle NPM aliases for @edx/brand (like MFEs); this work was never prioritized / ticketed in 2020…
- edx/edx-themes references brand-edx.org.
- For community/non-2U instances, the installed package is likely a no-op (nothing references it).
Removing @edx/brand-edx.org from package.json in edx-platform should likely go through DEPR process.
- Would likely break 2U/edX.org styles, if removed unintentionally.
edx-platform is running Paragon v2; will be difficult / impossible to upgrade to v23.
- No current plans to get to latest Paragon in edx-platform.
  - Has been attempted and deferred several times over the last 4 years.
- Instead, we’d like to get all the frontend out of edx-platform is the ideal situation, but not trivial/immediate…
  - XBlocks runtime will also be tricky.