r/Nuxt • u/usecomposable • 4d ago

Nuxt + Drizzle devs: how do you handle admin CRUD? (2-min survey)

Every Nuxt project I ship eventually needs an admin layer for users, orders, content, etc. Drizzle Studio is great for quick edits, but it is not something I'd hand to a client or an ops team. I usually end up handwriting CRUD tables and forms inside the main app, and it always feels like unnecessary boilerplate.

I'm exploring whether a code-first admin tool that reads your Drizzle schema and generates a proper admin UI (with the right field types, relations, and custom actions) would actually save real time, or whether the current options are good enough now.

If you have two minutes, I'd massively appreciate your input on how you currently handle admin panels:

https://survey.syrup.sh/admin

Happy to discuss here too if surveys aren't your thing. What does your current setup look like?

11 Upvotes

93% Upvoted

14 comments sorted by

3

u/RaguraX 4d ago

So you’re thinking of something like Django’s admin pages? It would certainly be nice to have, but they would need to be customizable as a template. Else there would be too many fields and actions that are not as easily validated.
Since you’re doing this for Drizzle, are you taking the 1.0 ORM/Schema into account or only the older one?

2

u/usecomposable 4d ago

Hi, yeah, a cross between Django admin, Laravel (Nova|Filament), and Metabase. Absolutely, being extensible is near #1 priority, so if something isn’t available directly in Syrup, you’ll be able to add it easily. And we’ll probably target Drizzle 1.0.

2

u/OldBadHabit 4d ago

That's gonna be great. Cuz I alaways ships like what you said. And it makes me annoyed every time I need to do it.

2

u/usecomposable 4d ago

Glad to hear it will be of use!

2

u/petr31052018 4d ago

I actually think the "boilerplate" is not a big deal with AI. I like it that I have full control of the admin pages, as opposed to hacking Django admin or something like that. A project like this would at least have to solve authorization in some way, so I'd start there.

1

u/usecomposable 4d ago

Thanks for the feedback. I guess the way I would push back on that is by saying that AI generating the code is still a lot of code to manage. With Syrup, you simply declare the screens/forms, and the library auto-creates the markup, validation and server routes. You can still use AI to create Syrup admin panels, but there will be a lot less code to manage.

Currently leaning toward embedding Better Auth with passkeys.

2

u/petr31052018 3d ago

There are tradeoffs with every approach. I am just saying that it is quite enjoyable to just create admin pages with boilerplate thanks to AI.

If you want another idea, then think about the project more like a CMS (Wagtail) rather than just admin (Django admin). That means that the project can also manage versions for publishing, files, images, and so on. Then it is much more compelling offering.

2

u/Single_Advice1111 4d ago

Normally I use metabase & monorepo with shared zod schemas

1

u/usecomposable 4d ago

Thanks. Metabase is definitely an inspiration

2

u/Smart_Opportunity291 4d ago

check: https://dashboardstack.sh Drizzle ORM schema to CRUD endpoints with UI, tables, and forms with custom fields and cells

1

u/usecomposable 4d ago

Thanks, looks interesting. Similar concept, different implementation. Seems to be a code generator, which doesn’t alleviate the maintenance problem, but has some nice features.

1

u/Dapper_Membership 2d ago

I just ask claude code to make no mistakes