You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I was preparing #1483 I stumbled about the dependency tree and structure of the UI-kit again.
Based on the outcome of #1484 and also further ideas how to improve the UI-kit, there needs to be a larger rebuild.
My idea is to provide the UI-kit frame to be a single application, either written in a framework or completely independent using web components. It has to be focused on one single framework, be it lit, svelt, solid or whatever. But the current implementation where we are using react, preact, lit and others is not a good way to maintain the project in the future.
Must haves:
Easy way to start in develop mode (Developer Experience)
Complete implementation in typescript (even if the development would have a slower pace)
When I was preparing #1483 I stumbled about the dependency tree and structure of the UI-kit again.
Based on the outcome of #1484 and also further ideas how to improve the UI-kit, there needs to be a larger rebuild.
My idea is to provide the UI-kit frame to be a single application, either written in a framework or completely independent using web components. It has to be focused on one single framework, be it
lit
,svelt
,solid
or whatever. But the current implementation where we are usingreact
,preact
,lit
and others is not a good way to maintain the project in the future.Must haves:
handlebars
IE11
orOpera Mini
which do not support basic standards)For all the changes we do, we should not forget to support the current features already in place.
The text was updated successfully, but these errors were encountered: