UI library for React project and long term plan #38
Replies: 2 comments 2 replies
-
I would say that Carbon has some limitations compared to Bootstrap and PrimeFaces (PrimeVue or PrimeReact). Here some of them: "
|
Beta Was this translation helpful? Give feedback.
-
In order for us to move away from Carbon, we need to demonstrate that whatever new system we pick can replicate what we are currently using from Carbon. No empty promises about infinite possibilities please. We need to see production level examples because SPAR is already using Carbon. In my mind, we need to see at a minimum: (This is not an exhaustive list)
With that work in mind, we then we have to evaluate how much work it would actually take to move off Carbon. Again, because SPAR is already using it. Then all the different FSA teams have to understand and absorb that level of work involved to move off Carbon. If it costs more time and effort to move from Carbon to another system, then it will not be a valuable move even if Carbon is not ideal. |
Beta Was this translation helpful? Give feedback.
-
Based on our recent discussion, we had some concerns with the Carbon UI library:
Previous thoughts of using Carbon for React project in FSA (when we already started SPAR):
Advantages of using Carbon:
Next step for React project (Jas & Craig):
Next step for common theme repo:
Next step for service designers and developers to discuss:
Beta Was this translation helpful? Give feedback.
All reactions