This is definitely not HTML first, though. This is TS first, JS second, CSS third, and only then, HTML last. I'm all for clean frameworks, but this is very far removed from the idea of putting HTML first.
But this franken <form> element requires JavaScript to even render. Same for the tooltip, leader, cover, totop, ++ components; all of which can be done with HTML and CSS.
Fine, write your HTML is JS, but that isn't "HTML first".
edit: I stand corrected. the form will render without JS. The tab element in the docs wrapping the form doesn't render.
I used it for a small form + search result list recently and it works well enough for simple / static stuff.
But I think I'll still be reaching for a JS lib first since I'd miss things like inputs-with-autocomplete too much.
It would seem that all other libraries want js for something as simple as a drop-down.
Cover, leader, dropdowns and even modals, you can always use the CSS class instead of UIkit custom attributes and toggle it manually via server.
The TypeScript and Tailwind insanities are just there for easier development and my convenience. ;)
Maybe soon, someone will publish the compiled CSS. IDK
But this is true for almost every web thing, and every web framework - you can just grab the final outputs and stick it into your web page.
So either your thing is "HTML-first", but so is everything else, or your thing is not "HTML-first", and some other things are.
> Maybe soon, someone will publish the compiled CSS.
So, until then, not only is this not HTML-first, it's not HTML at all.
To me (and maybe others), there's a difference between web development and Node/npm.
They are not one and the same.