\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
\uD83E\uDD45 Goals
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
CC | Core Contributor (Committer): Onboarding Tasks:
| ||
PR Review(s) | |||
| https://github.com/openedx/paragon/pull/2162 The auto-generated PR to sync | ||
Discoverable usage insights from component pages | https://github.com/openedx/paragon/issues/2179 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
- Adam Stankiewicz Review
@edx/brand-edx.org
PR - Adam Stankiewicz create
alpha
release in@edx/brand-edx.org
- Adam Stankiewicz add sprint iterations on GitHub board (Anastasiia Abyzova (Deactivated) may take a stab at this as well)
⤴ 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
.