Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

\uD83D\uDDE3 Discussion topics

Time

Item

Presenter

Notes

CC

Core Contributor (Committer): Onboarding

Tasks:

  • “Confirm that your employer has signed an Entity Contributor Agreement and identified you as an authorized submitter under that agreement.”

    • Not quite sure how to check this?

  • “If you don’t receive an invite [to CC Onboarding course), let us know by emailing cc-program-admins@tcril.org

PR Review(s)


alphamaster syncing


https://github.com/openedx/paragon/pull/2162

The auto-generated PR to sync alpha with master is showing merge conflicts.

https://github.com/openedx/paragon/issues/2170

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 index.scss files), but the compiled Paragon theme CSS can still be injected via @edx/frontend-platform.

We may need to swap our SCSS media queries in favor of using @custom-media instead.

@alpha is being used in production by eduNext (for better or for worse (wink))

Running out of backlog for tasks

  • Is there something other than design tokens the team can quick?

  • Viktor may focus on design tokens and there not many backlog items left for parallel workstream.

Potential ideas:

KPIs for devs:

Technical documentation

  • We’ll focus on design tokens docs for now.

We will use the Open edX

Grooming/sprints.

✅ Action items

⤴ 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 on alpha.
  • No labels