Page Comparison

10 minutes

Paragon CLI: install-theme

Adam Stankiewicz

[inform/demo] 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:

• https://github.com/openedx/frontend-template-application/pull/641

• Documentation in Paragon README

• Present/inform at 2U’s Solution Review

• Present/inform at FWG.

• Inform in various Slack channels (in Open edX and internal 2U Slack channels).

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).

Notes:

• 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?
    

5 mins

Form.Autosuggest Attributes

Mena Hassan

Draft PR: https://github.com/openedx/paragon/pull/2570#
^ this relies on some previous changes so it looks a little move involved than it actually is.

Checking to see if everyone is generally ok with the proposed changes

10 min

Floating labels & AutoSuggest

Jeff Witt

It’s weird, weird, and more weird.
- suggestion overwrite floating label (recent observation)
- Google moving floating label out of the way when there is a suggestion from the browser (how?)
- Chrome AutoSuggest positioning is different for different people
- Chrome AutoSuggest capture with Share Screen is different for different people

Requests:
- Use AutoSuggestAutoComplete attribute with granular semantic values
- Use AutoComplete whenever possible
- Store form results (particularly user data) and auto-populate fields when possible (WCAG 2.2 requirement)
-