2018-03-01 Meeting Notes
Date
Goals
| Time | Item | Who | Notes |
|---|---|---|---|
| 10 min | Status | Everyone | |
| 5 min | Reactstrap | Let's close the loop on last week's Paragon/Reactstrap discussion. | |
| Accessibility | Without Mark, what's our story for handling accessibility moving forward? | ||
| Theming vision/community engagement | Core FED has been chatting with community members about theming, and we met up with the Open team last week to discuss a clear vision for the future (notes here: 2018-02-27 Theming Meeting (FedX Core + Open Source)). We've got a rough idea of how we might want to approach this, but want to hear from you all (especially WL/Enterprise) about whether it makes sense for you. | ||
| 5 min | GitHub Tips | Jae |
Notes
- We have a cookiecutter now!! Make PRs: https://github.com/edx/front-end-cookie-cutter-application/
- Can we make use of dynamic module loading? (Stage-3 and will probably require a polyfill)
- Shared babelrc probably not worth it for now.
Reactstrap
- Paragon as design system
- Splitting up edx-specific stuff vs primitives
- Breaking up builds (everything vs. primitives-only)
Accessibility
- Unmeeting still happening!
- Should we discuss more as part of FedX?
- But FedX is usually pretty busy as-is
- Can we use our hour more effectively?
- Not everything is relevant to everyone
- Is this an important meeting?
- Unmeeting as accessibility office hours
- Can teams handle their own accessibility without a dedicated expert on staff?
- Where do people bring their a11y questions?
- FedX room
- a11y room
- Bring it to the unmeeting
- Where do people bring their a11y questions?
Theming
- Styling theming vs. comp theming
- WL uses comp theming to add features
- Should this be a switch?
- Comp theming limitations:
- Underscore doesn't work
- React won't work!
- Text theming – is this a thing we want to explore?
- Maybe?
- WL uses comp theming to add features
- Comp theming – partial templates
- Need small, stable API