Date
...
Agenda
Time | Item | Who | Notes |
---|---|---|---|
10 min | Status | Everyone | |
10 min | Issue review | Everyone | Check in on the status of issues (both in Paragon and elsewhere in the platform) |
5 min | GraphQL update | Ari | TL;DR: we ain't doing it. |
Theming OEP | Ari | This week I'm drafting a theming OEP. If anyone has input, let's capture it! | |
Paragon component-ization process | Dennis | What is the process for adding a component to paragon? A11y requirements/review? |
Notes
Paragon Componentization Process
- Dahlia has upcoming Listbox component
- How/whether to "propose" a component?
- How generic is it?
- API?
- Are there existing components that do this already?
- README PR (propTypes)?
- TODO: add this to documentation
- When to merge that component?
- One approval
- a11y review before merge
- DIY as much as possible, ask Jeff for trickier use cases
- Coverage reductions: when to fail?
- UX FYI (review if we feel it's necessary)
- Add this to docs
Theming OEP
- Whitelabel are stakeholders!!
- First: get rid of template overrides
- Ideal theming system:
- Override CSS
- Override logo
- Separate OEP for UI customization
- How to deprecate?
- Potentially preserve legacy template override system before killing it
- Date of death?