erichartline
commented
6 years ago So the general idea is to allow the user to pull buttons as necessary rather than use a single Login component (i.e. import { GoogleButton, OrcidButton } etc).
Things to do:
- [ ] Open up the buttons
- [ ] Avoid overriding styles unless absolutely necessary
- [x] Remove width from CSS, this should fill the parent component
- [x] Add click handlers
- [ ] Use a HOC or render props (if not, expose the subroutine)
- [ ] Should be natural use of MUI, not forceful
- [ ] Expose the button generator function (use HOC or render props here)
- [x] Add ORCID icon (found at academicons)
Start with the simple plan first (not necessarily easy!)
Should we allow the user to choose from a specified allotment of buttons (i.e. Google, Facebook, etc), or do we give them the option to create their own button by passing in styles, icon, etc?
Each button when clicked will trigger an action (function) that should be opened in the interface.