2018-02-22 Meeting Notes
Date
Goals
| Time | Item | Who | Notes |
|---|---|---|---|
| 10 min | Status | Everyone | |
| 59 seconds | Paragon Storybook Minute | Jae | https://github.com/edx/paragon/pull/150 |
| 5 minutes | edX Cookie Cutter | Jae | https://github.com/jaebradley/edx-cookie-cutter |
| Telling the Bootstrap story | Milk and Honey covers greenfield systems-level design, but what's our plan for handling and maintaining styling going forward? I've taken a rough stab at prioritizing and summing up the work we've been discussing – let's discuss and fill in gaps. | ||
| Paragon as reactstrap | Let's talk about Tyler's idea for a Paragon based on reactstrap. What does everyone think? How might we approach an implementation like this? |
Notes
Cookiecutter
- Todo:
- Docker stuff
- CSS stuff
- Tests
- Deployment flow
- Linting
- Boilerplate cleanup command
- Track all this via GH issues
Reactstrap
- Paragon asInput form group makes customization difficult
- Many Paragon-ish things already exist in Reactstrap
- Lots of peer dependencies – added bloat?
- Are there alternatives?
- API easy to use
- Easy to build on top of
- Do we really need Reactstrap?
- Just a lightweight stateless wrapper on top of Bootstrap classnames
- Overkill?
- Easy for non-FEDs to understand
- What if we're making a static HTML page?
- Division: Paragon components vs. Bootstrap components
- Is this implementation split a major issue?