2023-10-20 Meeting notes

Ready for review

@Vladyslav Zadorozhnii

@Peter Kulko

Master:

• [BD-46] feat: defined types for Paragon export by monteri · Pull Request #2566 · openedx/paragon

• Extend Form.Control with input mask · Issue #2458 · openedx/paragon

• [BD-46] fix: hover for danger button by khudym · Pull Request #2675 · openedx/paragon

• [BD-46] fix: do not override `SearchField` styles by viktorrusakov · Pull Request #77 · edx/brand-edx.org

• [BD-46] feat: change outline primary btn color by khudym · Pull Request #78 · edx/brand-edx.org

• [BD-46] docs: update color picker readme by khudym · Pull Request #2646 · openedx/paragon

• [BD-46] feat: move CLI design tokens commands to paragon CLI by monteri · Pull Request #2609 · openedx/paragon

• [BD-46] docs: added link to Contrast Checker tool by PKulkoRaccoonGang · Pull Request #2726 · openedx/paragon

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

• [OLD] feat: Chip component redesign by PKulkoRaccoonGang · Pull Request #2713 · openedx/paragon- Chip component redesign.

Alpha:

• [BD-46] refactor: refactoring buttons variants by PKulkoRaccoonGang · Pull Request #75 · edx/brand-edx.org

• [BD-46] chore: merging master into alpha by PKulkoRaccoonGang · Pull Request #2731 · openedx/paragon - synchronize alpha branch to master

Issues

@Peter Kulko

• [BD-46] Duplicate Menu component name · Issue #2689 · openedx/paragon

• [alpha] The primary IconButton component does not have a white background · Issue #2688 · openedx/paragon

• [BD-46] Going to a non-existent page after clicking on Breadcrumbs links · Issue #2684 · openedx/paragon

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

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

Replacement for deprecated components

@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

https://github.com/openedx/paragon/pull/2715
or
https://github.com/openedx/paragon/pull/2734

Decision: We will prefer the former PR.