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 4 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

\uD83D\uDDE3 Discussion topics

Time

Item

Presenter

Notes

10 minutes

Paragon CLI: install-theme

Adam Stankiewicz

[inform] We recently released a new Paragon CLI. It comes with a single command to start: paragon install-theme

Allows consumers to install and use a custom @edx/brand aliased NPM package during local development without risking modifying/committing changes to the default installed @edx/brand-openedx package.

Example:

{
  "scripts": {
    "build:with-theme": "paragon install-theme && npm build",
    "start:with-theme": "paragon install-theme && npm start",
  }
}

Next steps:

Future CLI ideas:

Our roadmap includes:

  • Porting over existing CLI tools into the new Paragon CLI as additional commands.

    • Component generator

    • [design tokens] SCSS variables → CSS variables migration

  • Tracking Segment events when these CLI commands are used by consumers.

  • Automated migrations for consumers (i.e., dealing with breaking changes).

10 min

Label association

Mena Hassan

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

  • Can we move forward with the proposed fix?

  • How do we feel about labels?

  • Would be good to know if there's a preferred pattern or are we going to just need to make some exceptions here?

    • When we make exceptions, what's the criteria for that?

✅ Action items

  •  

⤴ Decisions

  • No labels