In the giving-frontend project, I actually used several components from theme-ui directly instead of adding them to @cu-advancement/component-library and then using them. Furthermore, 'theme-uihas TypeScript support...and usingreact-hook-form` with TS and a component library makes it more verbose and harder to prototype.
Coupled with all this, adding tables will be outside of the scope of theme-ui which the component library is based on. For forms, I'm going ahead and just using native inputs instead of custom ones, and I'll do the same for tables as well. At some point in the future, the styling can be improved, but it's not really needed for the CMS side of things.
Required
Acceptance Criteria
[ ] Replace @cu-advancement/component-library with theme-ui
In the giving-frontend project, I actually used several components from
theme-uidirectly instead of adding them to@cu-advancement/component-libraryand then using them. Furthermore, 'theme-uihas TypeScript support...and usingreact-hook-form` with TS and a component library makes it more verbose and harder to prototype.Coupled with all this, adding tables will be outside of the scope of
theme-uiwhich the component library is based on. For forms, I'm going ahead and just using native inputs instead of custom ones, and I'll do the same for tables as well. At some point in the future, the styling can be improved, but it's not really needed for the CMS side of things.Required
Acceptance Criteria
@cu-advancement/component-librarywiththeme-uitheme-ui