Page Comparison

Ready for review

Vladyslav Zadorozhnii

Peter Kulko

Master:

• https://github.com/openedx/paragon/pull/2566#pullrequestreview-1595674383

• https://github.com/openedx/paragon/issues/2458

• https://github.com/openedx/paragon/pull/2675#pullrequestreview-1661693554

• https://github.com/edx/brand-edx.org/pull/77

• https://github.com/edx/brand-edx.org/pull/78

• https://openedx.atlassian.net/l/cp/8FmHZHaD - added notes about the ability to edit accessibility attributes.

• https://github.com/openedx/paragon/pull/26462713- Chip component redesign.

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

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

• https://github.com/openedx.atlassian.net/lparagon/cp/8FmHZHaD - added notes about the ability to edit accessibility attributes.pull/2749

• https://github.com/openedx/paragon/pull/2713- Chip component redesign.

Alpha:

• 2719

• https://github.com/edx/brand-edx.orgopenedx/paragon/pull/752617

Alpha:

• https://github.com/openedx/paragonedx/brand-edx.org/pull/2731 - synchronize alpha branch to master75

Issues

Peter Kulko

• https://github.com/openedx/paragon/issues/2689

• https://github.com/openedx/paragon/issues/2688

• https://github.com/openedx/paragon/issues/2684

• https://github.com/openedx/paragon/issues/2694

• https://github.com/openedx/paragon/issues/2706

Replacement for deprecated components and other docs for design tokens migrations

Vladyslav Zadorozhnii

• Sanity check: verify that all deprecated components getting removed have an associated component to migrate to.

• Create list of deprecated components and which components to migrate to.

  • Possibly include code snippet for each as a simple example.

  • Possibly refer to Usage Insights to understand current usage of deprecated components to ensure all functionality in deprecated components is accounted for.

• We will ensure this documentation is included in the design tokens release notes in the the GitHub release.

Database for tokens

Vladyslav Zadorozhnii

• Would probably need to be a system for this.

• SQL vs NoSQL?

• Generate CSS file from database.

• Display tokens as documentation from database values?

• Potential concern is how to automate the hosting of CSS files generated (e.g., 2U/edX plans to use jsDelivr for now, CSS file in Paragon repo (brand-edx.org repo).

• We’ll come back to this as the need arises; it does seem relevant to be able to support some future use cases, though.

Brian’s solution is probably the better one

Vladyslav Zadorozhnii

Updated documentation

• deprecated components

• font awesome

• CLI docs

• demo collapsible headings for the confluence docs

Upgrade gatsby to v5

Vladyslav Zadorozhnii Peter Kulko

• Discussed on the PWG and Brian Smith proposed to divide the PR into smaller parts https://github.com/openedx/paragon/pull/

• 2767

• Runs out of memory and is not successful for development

• There are results in the PR comment

REST API for overriding design tokens using

Vladyslav Zadorozhnii

Updated utility functions docs

Peter Kulko

https://githubdocs.google.com/openedxspreadsheets/paragond/pull/2734Decision: We will prefer the former PR.1DtEdJcICiUJTeQOAUSGmSurUy95XlLItwuiJJfYZJj8/edit#gid=0

transitions in the Paragon

Vladyslav Zadorozhnii

Discussed on the PWG with Jeff Witt (Deactivated)