Laravel Nova

You are a Laravel Nova expert. The user wants to customize Laravel Nova admin panels with custom fields, actions, filters, and resource configurations.

What to check first

• Run php artisan nova:install to verify Nova is installed in your Laravel project
• Check config/nova.php exists and review the namespace and path configurations
• Verify you have a app/Nova directory where resource classes are stored

Steps

1. Create a new Nova resource by running php artisan nova:resource Post — this generates app/Nova/Post.php with fields, actions, and filters
2. Define searchable and sortable fields in the resource's fields() method using Text, Textarea, Select, BelongsTo, and BelongsToMany field classes
3. Add custom actions to the actions() method by extending Laravel\Nova\Actions\Action and implementing the handle() method
4. Create custom filters by running php artisan nova:filter PublishedFilter and adding them to the resource's filters() method
5. Customize the resource's cards() method to add dashboard metrics using built-in cards like ValueMetric, TrendMetric, and PartitionMetric
6. Override the indexQuery(), detailQuery(), and creationQuery() methods to customize Eloquent queries with scopes, eager loading, or authorization checks
7. Register custom Field classes in the resource by extending Laravel\Nova\Fields\Field and implementing resolve() and fill() methods
8. Register resources in app/Providers/NovaServiceProvider.php by adding them to the resources() method array

Code

<?php

namespace App\Nova;

use Laravel\Nova\Fields\ID;
use Laravel\Nova\Fields\Text;
use Laravel\Nova\Fields\Textarea;
use Laravel\Nova\Fields\Select;
use Laravel\Nova\Fields\BelongsTo;
use Laravel\Nova\Fields\DateTime;
use Laravel\Nova\Actions\ExportAsCsv;
use Laravel\Nova\Filters\Select as SelectFilter;
use Laravel\Nova\Http\Requests\NovaRequest;

class Post extends Resource
{
    public static $model = \App\Models\Post::class;
    public static $title = 'title';
    public static $search = ['id', 'title', 'slug'];

    public function fields(NovaRequest $request)
    {
        return [
            ID::make()->sortable(),
            
            Text::make('Title')
                ->sortable()
                ->rules('required', 'string', 'max:255'),
            
            Text::make('Slug')
                ->rules('required', 'string', 'unique:posts,slug'),
            
            Textarea::make('Content')
                ->alwaysShow()
                ->rules('required'),
            
            Select::make('Status')
                ->options([
                    '

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change