kyoto VS uikit

the only thing i need to do is port the htmx code to golang and then cross compile to wasm for web and then to mobile and desktop. I am currently seeing that there are other htmx style systems out there that are already written n golang. for example: https://github.com/kyoto-framework/kyoto

But this baby here https://github.com/kyoto-framework/kyoto is in the early development stages, which is a nice approach imho.

htmx requires you to return markup for specific components. So, you’ll need to maintain component template definition in two ways: embed directly into page template, and serve it as an api. IMO htmx is cool, but requires some tooling around it to simplify work. Our team is developing and using kyoto library, focused on server rendering and components approach: https://github.com/kyoto-framework/kyoto

UIKit (WIP): https://github.com/kyoto-framework/uikit

UIKit (in active development): https://github.com/yuriizinets/kyoto-uikit

Started development of UI Kit. High-level components library that tries to bring fully featured components, like navbar, sidebar, statistics, headings, forms and so on. We are trying to avoid low-level components like buttons/inputs/selects as far as we think that low-level things can be made without components at all. Library now in active development and not recommended for using. We are trying to find out main problems while implementing components as a separate package.