Is there any need for tailwind-based components that are just pure html, or would you want something more functional, or nothing at all?

I think Osty is doing something with that nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7 ? and nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg was working on something like that?

Reply to this note

Please Login to reply.

Discussion

Jsx would be nice, I'm always looking for tailwind components as examples.. (it's practically just html). Mostly I just go to Daisy and try to piece things together..

I think HTML with Tailwind would make sense as it can easily used in React or Svelte apps.

Verbiricha is building ngine based on ChakraUI (React based) and he also has a Storybook with components ... but I think its not hosted publicly yet.

I’ll check out storybook

this would be useful for us and others imo. I'm planning to move ngine away from Chakra UI to something that doesn't require CSS-in-JS before official release, probably Radix.

nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg maybe even consider separating the UI components from the core code (hooks, context, ..) and release it as a separate package ngine-core? Would be easier to use with a different UI library.

great suggestion, this is planned!

What about Tailwind + HTMX ?

I think pure html+css components are not useful enough. we need more complex components like dropdowns, modals, popovers, menus, and so. I found radix-ui, and shadcn-ui more practical for a complete set of components. and regarding the #Osty, I'm creating common components based on nostr-design.

Thanks for your feedback. I agree, pure HTML basic components can be found in many frameworks and it makes no sense recreating them.