Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Kishore032's avatar

Using Nova as customer facing UI (not just admin)

All -

This is both to share my experience with Laravel Nova and to ask for help with a couple of issues.

First, the story: I am relatively new to Laravel and I heard of Nova as a framework for "admin dashboards." I played with it for a couple of days and quickly realized that it can in fact be a pretty powerful UI framework. And Nova came through for me. For someone who was new to Laravel, not to mention Nova, it took me about 3 weeks to build a UI for a relatively sophisticated AI-based email app and advance the launch date for my app to April from June. The point of the story is that Nova - at least in my naive opinion - is a lot more than an admin dashboard.

Second, my questions:

(a) I use the standard Laravel "{!! !!}" to render html email, some of which include their own CSS & scripts (as I said, it's an email application). Is there a way I can confine the scope to these CSS and scripts to what's inside {!! !!}}? The scripts seem less of a problem, but I am having a hell of a time with CSS, particularly if the email is coming from an MS Outlook server.

(b) Nova seems to respect Laravel "Policy" well, except when it comes to "Actions". Within Actions, Nova seems to not allow things that are allowed in the Policies; and at the other extreme, a "can run" seems to be able to override Laravel Policies. My question is: where should I be specifying the policies - as part of the resource in Laravel or at the UI level within Nova?

For context: the site is elfpoint.com and I have set up a demo account (u: demoelf, p: demoelf) that you can log into directly.

Thank you and I appreciate any help.

Kishore

0 likes
0 replies

Please or to participate in this conversation.