t3-turbo-and-clerk VS daisyui

In this tutorial, we will implement single sign-on using Clerk, and use GitHub as the OAuth server that'll verify the user’s credentials. We are going to modify an existing application to add protected routes and use the pre-built UI components.

Clerk official example using Nextjs & expo: (no express, webhooks or credential auth) https://github.com/clerk/t3-turbo-and-clerk

I’m currently checking out https://clerk.dev, seems pretty decent so far. The pricing model isn’t ideal but apparently they are redoing it at this moment.

t3-turbo-and-clerk

If you want a complete out of the box easy setup for web and mobile, check this rep out https://github.com/clerkinc/t3-turbo-and-clerk

No I signed up with clerk.dev which made it a lot easier. tbh if it wasn't for them I would have had to hire a developer to help set that up because I had no idea about auth, user databases, and all that.

Some open-source identity solutions I learned could help; integrate with the Logto /Clerk, Ory... API to securely store access tokens that allow Chat GPT to access the user's Logto account; this is a start. But, like these, Security and privacy of service / Technical requirements for integration / User interface for authorization, there’s much to do. It's funny to rethink this topic.

https://clerk.dev meets all of your requirements except ABAC and OSS/self-host. Recommend checking it out if you want something that "just works"

I've def felt your pain before, and it's why I started https://clerk.dev - auth "should just work".

DaisyUI offers zero-JS components

https://daisyui.com/

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.

Tailwind is great, but creating everything from scratch is annoying. A nice base of components which can be extended with tailwind would be great. There are a few tailwind frameworks like Flowbite, Daisy Ui, but I like Bulma, PicoCSS and Bootstrap.

While I have experience with Tailwind and frontend development, I don’t really have the patience to use it. I usually end up using something like Mantine, which is a complete component library UI kit, or Daisy UI, which is a component library built on top of Tailwind. Shadcn/ui is quite similar to Daisy in this sense, but being able to customize the individual components, since they get installed to your components folder, made development more streamlined and more customizable. On top of that being able to change my components style with natural language thanks to v0 made development super easy and fast. Shadcn may be too minimalist of a style for some, but thanks to all the components being local, you can customize them quickly and easily!

https://daisyui.com is a really great middle ground—you can move as fast as you would in Bulma, then drop down into the weeds with TW if you need it.

If you're looking for grab and go components, Daisy UI or Flowbite might be more your speed, I've used both with minimal headache.

https://daisyui.com/

This guide is tailored for front-end developers looking to explore the smooth integration of DaisyUI's stylish components, Alpine.js's minimalist reactive framework, and the straightforward back-end capabilities of Codehooks.io.

Others:

  - https://daisyui.com/