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.
HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
121–130 of 193 posts
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#122Foolish of me to think "HTML-first" meant it wouldn't require nodejs/npm and that dependency hell.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#123This 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.
I'd really like a set of elements like this that is truly HTML + CSS. Vanilla. Layer on some _optional_ JS for some enhancements.
But this franken 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.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#124This made me want to unlearn react.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#125This 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.
Let me disagree. This is HTML-first because you can always grab the compiled CSS and optionally, compiled JS and reference it in your plain HTML file via and it will work just fine.
The TypeScript and Tailwind insanities are just there for easier development and my convenience. ;)
Maybe soon, someone will publish the compiled CSS. IDK
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#126This 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.
I'd really like a set of elements like this that is truly HTML + CSS. Vanilla. Layer on some _optional_ JS for some enhancements. But this franken 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 el…
The form does not need JS. There are two labels black and red "Requires JS". The black one should've been "May Require JS". It is use for the "custom controls" provided by UIkit. But it is not required.
Cover, leader, dropdowns and even modals, you can always use the CSS class instead of UIkit custom attributes and toggle it manually via server.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#127This 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.
I'd really like a set of elements like this that is truly HTML + CSS. Vanilla. Layer on some _optional_ JS for some enhancements. But this franken 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 el…
DaisyUI offers zero-JS components
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.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#128> framework-agnostic > Franken UI is a Tailwind CSS plugin :|
As someone using Svelte for a project, I'm always happy to see something less React-specific. But yeah, I'm kinda over Tailwind. You whipper-snappers think CSS sucks so much; back in my day* we had font tags and tables! *high school
Yeah I know it’s crotchety old man territory but I find CSS absolutely fine to work with these days, now that we have variables etc. Every time I’ve added PostCSS, Tailwind or whatever I’ve found my build times jump a ton and I don’t get a whole lot of use out of it.
Plain CSS and containerisation provided by Svelte (or the forthcoming scope stuff) is more than enough for me.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#129Earlier quoted context omitted.
I'd really like a set of elements like this that is truly HTML + CSS. Vanilla. Layer on some _optional_ JS for some enhancements. But this franken 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 el…
The form does not need JS. There are two labels black and red "Requires JS". The black one should've been "May Require JS". It is use for the "custom controls" provided by UIkit. But it is not required. Cover, leader, dropdowns and even modals, you can always use the CSS class instead of UIkit custom attributes and toggle it manually via server.
Ah so the tab component doesn't render without JS. Because I can't see the form render in the docs. Which is in a tab.
Tabs can also be plain HTML + CSS. Even easier now with :has
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#130Earlier quoted context omitted.
As someone using Svelte for a project, I'm always happy to see something less React-specific. But yeah, I'm kinda over Tailwind. You whipper-snappers think CSS sucks so much; back in my day* we had font tags and tables! *high school
Yeah I know it’s crotchety old man territory but I find CSS absolutely fine to work with these days, now that we have variables etc. Every time I’ve added PostCSS, Tailwind or whatever I’ve found my build times jump a ton and I don’t get a whole lot of use out of it. Plain CSS and containerisation provided by Svelte (or the forthcoming scope stuff) is more than enough for me.
CSS is a dream these days. I understand why it’s intimidating for devs because it’s not meant for engineers it’s meant for designer so it has a wildly different set of assumptions and expectations.
But learning it is 100% worth it.
Tailwind is like an ORM. I get the appeal but if you know SQL /CSS it’s just going to get in the way.