Historically, several years ago, kytos team used to have exclusive full-time front-end and designers to build an UI, from the layout to every reactive component. This ended up very well designed, but since we don't have exclusive front-end and designers anymore it can be time consuming to keep up maintaining all existing components and fixing minor bugs like input selection issues, or having to implement new filter on tables, or even have to implement a new component from scratch.
Can we we leverage a battle tested library to simplify certain kytos components and easier to keep up with upstream with minimal changes while still having compatible CSS styling and coexisting with kytos components layout? and then instead of importing certain k-* components then we import an styled compatible component.
It'd be great if we could import battle tested and upstream updated/newer components. For instance, could we use (and mix) any of these ones below?
Historically, several years ago, kytos team used to have exclusive full-time front-end and designers to build an UI, from the layout to every reactive component. This ended up very well designed, but since we don't have exclusive front-end and designers anymore it can be time consuming to keep up maintaining all existing components and fixing minor bugs like input selection issues, or having to implement new filter on tables, or even have to implement a new component from scratch.
Can we we leverage a battle tested library to simplify certain kytos components and easier to keep up with upstream with minimal changes while still having compatible CSS styling and coexisting with kytos components layout? and then instead of importing certain
k-*components then we import an styled compatible component.It'd be great if we could import battle tested and upstream updated/newer components. For instance, could we use (and mix) any of these ones below?