Page Comparison

...

\uD83D\uDDE3 Discussion topics

Environment: frontend-app-account
frontend-platform: slight modifications to achieve application render and have paragon core + theme, brand core + theme.
frontend-build: slight modifications to achieve brand light.min.css to appear in the <head>
Current only issue is due to the rel="preload" is not replaced to rel="stylesheet"

Time

Item

Presenter

Notes

Merged PRs:Open PRs

Vladyslav Zadorozhnii

Other updates

Vladyslav Zadorozhnii Peter Kulko

Open PRs
https://github.com/openedx/paragon/pull/

2496

1498 Multiselect
There was requirements to create design for Multiselect . Any progress?

Dark theme variant?
Need to check-in with Gabe + Chip designs (blocking implementation to resolve Chip as currently implemented).
- Should be design’s highest priority with Paragon backlog.

https://github.com/openedx/paragon/pull/

2378

2013 table of content

[Adam] Reviewed.

https://github.com/openedx/paragon/pull/

2495

Reviewed PRs:1911 Pagination component

https://github.com/openedx/paragon/pull/

2013

2177 Define Types

[Adam] Reviewed.

https://github.com/openedx/paragon/pull/

2460

Update on style inhering (decoupling Paragon from *-header/footer components)

Vladyslav Zadorozhnii

2379 we continue rebasing sync?

Skeleton fix

https://github.com/openedx/paragon/issues/2389 button statespull/2531

SCSS flags

Vladyslav Zadorozhnii

https://github.com/openedx/paragon/pull/2177 typescript export2423

what are the steps to inform community?
- [Adam] Example:
  - https://github.com/openedx/

paragon

- - public-engineering/issues/

2366 The Leave feedback link has moved down

- - 195
  - https://

github

- - discuss.

com/

- - openedx.org/

paragon/pull/2423 needs discussion on strategy for deprecation

[Adam] My two cents:

Remove the global SCSS flags altogether. Loop it in with the breaking change for alpha anyways.
Create a DEPR ticket describing the removal of these global SCSS flags, what it means for consumers, and how those things should be configured in a world with design tokens.
- Doubt there will be much push back given these global flags aren’t really used by theme authors.
  - t/deprecation-removal-enzyme-public-engineering-195/10259
- [Adam] I can take this on as an action item so you can stay focused on implementation.
and for places where some flags are used like this, do we open PR? In this case flag is used in brand-edx.org and it is $enable-shadows: true !default; so it means we go to brand-openedx and override all shadows to none , like:

Code Block
# on the top of _variables.scss :root { --pgn-elevation-box-shadow-centered-5: none; --pgn-elevation-box-shadow-centered-4: none; --pgn-elevation-box-shadow-centered-3: none; and so on ... }

Maybe I am missing something…

[Adam] brand-openedx repo itself will continue to not define any custom design tokens; instead, it acts as a template for brand authors to clone/create their own brands. Since Paragon’s default SCSS has $enable-shadows: false, we should continue to adhere to that and ensure no tokens defined in the Paragon repo has shadows configured. That said, we should ensure any shadows are applied for brand-edx.org repo.

Migration docs + suggestion for CLI update to incapsulate commands for migration

Vladyslav Zadorozhnii

Updated docs a bit
Migrating MFEs to Paragon design tokens and CSS variables

New issues

Peter Kulko

https://github.com/openedx/paragon/pull/2495 new opened PR for custom media queriesissues/2519

[Adam] MergedADAM] GREAT CATCH! YES.

https://github.com/openedx/paragon/pull/2376 common.css/issues/2520

Brand and *-header/footer PRs

Vladyslav Zadorozhnii Peter Kulko

OpenEdx Frontend-component-header -

https://github.com/openedx/frontend-component-header/pull/351

OpenEdx Frontend-component-footer -

https://github.com/openedx/paragon/issues/2420 Skeleton issue to current new sprint?[Adam] Yes. Moved into current sprint.
frontend-component-footer/pull/303