| | | |
|---|
| Ready for review | @Vladyslav Zadorozhnii @Peter Kulko | Master: Alpha: |
| Issues | @Peter Kulko | |
| 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 |
or
Decision: We will prefer the former PR. |