2023-04-07 Meeting notes
Date
Apr 7, 2023
Participants
@Adam Stankiewicz
Goals
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
| CC |
| Core Contributor Onboarding (Coding roles) Tasks:
|
| PR Review(s) |
| |
| sync: master to alpha by edx-requirements-bot · Pull Request #2162 · openedx/paragon The auto-generated PR to sync Resolve conflict between `master` and `alpha` · Issue #2170 · openedx/paragon | ||
| Discoverable usage insights from component pages |
| Brian Smith from Axim (FKA tCRIL) provided a great suggestion to make “Usage Insights” data discoverable from component pages. This would help consumers more easily understand how “production-ready” a component is (since most aren’t aware “Usage Insights” page exists) and to find actual code examples beyond the code snippets in the docs site. Treat this issue as a discovery story, with the output being a new Github issue created with details about a recommendation on what to implement. |
| CSS variables & media queries |
| We will try leaving the compilation of @custom-media style definitions up to the MFEs (via their We may need to swap our SCSS media queries in favor of using |
|
|
|
|
|
|
| Running out of backlog for tasks
Potential ideas: |
|
|
| KPIs for devs:
|
|
|
| Technical documentation
|
|
|
| We will use the Open edX #wg-paragon board. Still would like to connect #wg-paragon with RG Slack workspace.
|
|
|
| Grooming/sprints.
|
Action items
@edx/brand-edx.org
PRalpha
release in @edx/brand-edx.org
Decisions
- If there is a PR merged to
master
with SCSS variables that are added/changed, file a follow-up issue in Github to account for the change in the design tokens onalpha
.