```
### Add DataTables Integration
```blade
@push('scripts')
@endpush
```
### Change Colors
Edit CSS classes:
```blade
```
---
## Architecture
### Separation of Concerns
```
Request → Controller → Service → Repository → Database
↓
Form Request (Validation)
Response ← View (Blade + Tailwind)
```
### File Organization
```
app/Repositories/{Model}/
├── {Model}RepositoryInterface.php # Interface
└── {Model}Repository.php # Implementation
app/Services/
└── {Model}Service.php # Business logic
app/Http/Controllers/
└── {Model}Controller.php # HTTP handling
app/Http/Requests/{Model}/
├── Store{Model}Request.php # Create validation
└── Update{Model}Request.php # Update validation
resources/views/app/{model}/
├── index.blade.php # List
├── create.blade.php # Create form
├── edit.blade.php # Edit form
└── show.blade.php # Details
routes/web.php
└── Route::resource(...) # RESTful routes
```
### Data Flow
**Create Flow:**
```
GET /products/create
↓ (Load form)
ProductController::create()
↓ (Return view)
create.blade.php
↓ (User fills form & submits)
POST /products (store)
↓ (Validate)
StoreProductRequest
↓ (Process)
ProductController::store()
↓ (Save via service)
ProductService::create()
↓ (Store in DB via repository)
ProductRepository::create()
↓ (Redirect)
/products/{id} (show)
```
**Edit Flow:**
```
GET /products/{id}/edit
↓
ProductController::edit()
↓ (Pre-populate form)
edit.blade.php
↓ (User updates & submits)
PUT /products/{id} (update)
↓ (Validate)
UpdateProductRequest
↓ (Process)
ProductController::update()
↓ (Update via service)
ProductService::update()
↓ (Update in DB via repository)
ProductRepository::update()
↓ (Redirect)
/products/{id} (show)
```
---
## Sidebar Management
The sidebar is driven by `config/sidebar.php`. The generator automatically appends an entry to that file:
```php
// config/sidebar.php
[
'label' => 'Products',
'route' => 'products.index',
'icon' => 'shopping_cart',
'active_pattern' => 'products.*',
],
```
The sidebar blade component loops over this config, so no HTML is injected into the view.
### Remove Sidebar Item
When you delete a CRUD with `php artisan delete:rsc Product`, the config entry is automatically removed.
**Manual removal:** Delete the matching array entry from `config/sidebar.php`.
---
## Service Provider Binding
The generator automatically adds bindings to `app/Providers/AppServiceProvider.php`:
```php
$this->app->bind(
ProductRepositoryInterface::class,
ProductRepository::class
);
```
When you delete with `php artisan delete:rsc Product`, bindings are automatically removed.
---
## Troubleshooting
### Issue: Migration errors during column creation
**Problem:** Invalid column type or configuration
**Solution:**
1. Use `back` command to remove the problematic column
2. Check column type is valid (string, integer, decimal, etc.)
3. For decimal, ensure precision > scale
4. Re-add the column with correct settings
```
Column name: price
Column type: decimal
Precision (total digits) [8]: 10
Scale (decimal places) [2]: 2 ← Must be ≤ 10
```
### Issue: Input type not matching column type
**Problem:** Form field type doesn't match database type
**Solution:**
1. The generator suggests appropriate input types automatically
2. If wrong type was selected, manually edit the blade file
3. Or delete and regenerate with correct input type
```bash
# Delete and regenerate
php artisan delete:rsc Product
php artisan make:rsc Product --label="Products"
```
### Issue: Views not rendering
**Problem:** Blade files not found
**Solution:**
1. Verify view path matches `--view-path` option
2. Check files exist in `resources/views/app/` (default) or custom path
3. Ensure model name matches view folder (kebab-case)
```bash
# Check actual paths
ls resources/views/app/product/
ls resources/views/admin/product/ # if --view-path=admin used
```
### Issue: Generation failed and files were cleaned up
**Problem:** Error occurred during generation, all files automatically deleted
**Solution:**
1. Check the error message for details
2. Common causes:
- Invalid migration (duplicate column, syntax error)
- Disk permissions issue
- Database connection problem
3. Fix the issue and run `make:rsc` again
```bash
# If migration was the issue, retry from scratch
php artisan make:rsc Product --label="Products"
```
### Issue: Deletion didn't remove everything
**Problem:** Some files/config still exist after delete:rsc
**Solution:**
1. Delete command removes what it can find
2. If you manually edited files, delete them manually:
- Custom blade files
- Modified routes
- Custom repository methods
3. Check `config/sidebar.php` for orphaned menu entries
```bash
# Verify what was deleted
git status # See what files changed
grep -r "Product" routes/web.php # Check if routes removed
grep -r "ProductRepository" app/Providers/AppServiceProvider.php
```
### Issue: Form validation errors not showing
**Problem:** Error messages don't appear
**Solution:**
1. Verify Form Request class exists
2. Check validation rules are defined
3. Ensure error messages in blade template
4. Check form has `method="POST"` with CSRF token
```php
// app/Http/Requests/Product/StoreProductRequest.php
public function rules(): array
{
return [
'name' => 'required|string|max:255',
'price' => 'required|decimal:0,2',
];
}
```
```blade
@if ($errors->any())
@foreach ($errors->all() as $error)
{{ $error }}
@endforeach
@endif
```
### Issue: Styles not applying
**Problem:** Tailwind classes not working
**Solution:**
1. Rebuild CSS: `npm run build`
2. Or run dev watcher: `npm run dev`
3. Check no CSS conflicts
4. Verify dark mode meta tag in layout
5. Clear browser cache
```bash
# Build once
npm run build
# OR watch for changes
npm run dev
```
### Issue: Routes not automatically added
**Problem:** Routes missing from `routes/web.php`
**Solution:**
1. Generator tries to add routes automatically
2. If it fails, add manually:
```php
// routes/web.php
use App\Http\Controllers\ProductController;
Route::middleware(['auth', 'verified'])->group(function () {
Route::resource('products', ProductController::class);
});
```
**Verify routes exist:**
```bash
php artisan route:list | grep product
```
### Issue: Service provider binding not added
**Problem:** Dependency injection fails
**Solution:**
1. Generator automatically adds binding
2. If missing, add manually to `AppServiceProvider.php`:
```php
public function register(): void
{
$this->app->bind(
\App\Repositories\Product\ProductRepositoryInterface::class,
\App\Repositories\Product\ProductRepository::class
);
}
```
### Issue: Sidebar item not showing
**Problem:** Menu item missing from sidebar
**Solution:**
1. Check `config/sidebar.php` — the generator appends an entry here
2. If missing, add manually:
```php
// config/sidebar.php
[
'label' => 'Products',
'route' => 'products.index',
'icon' => 'shopping_cart',
'active_pattern' => 'products.*',
],
```
### Issue: Database table already exists
**Problem:** Migration fails because table exists
**Solution:**
1. Generator prompts to drop existing table
2. Choose yes to recreate
3. Or drop manually:
```bash
php artisan migrate:refresh # Drop all tables
php artisan migrate # Re-run all migrations
```
### Issue: Column already exists in table
**Problem:** Can't add column to existing table
**Solution:**
1. Use `--repository-service-only` to skip migration
2. Or manually create a new migration:
```bash
php artisan make:migration add_columns_to_products_table
```
```php
Schema::table('products', function (Blueprint $table) {
$table->string('new_column')->nullable();
});
```
---
## Statistics
| Metric | Count |
|--------|-------|
| Console Commands | 2 (make:rsc, delete:rsc) |
| Generator Classes | 7+ |
| Blade files per CRUD | 4 |
| Supported column types | 13 |
| Input type options | 10+ |
| Generated files per CRUD | 8 |
| Dusk test cases | 11+ |
| Auto-generated screenshots | 11+ |
| Tailwind utilities used | 50+ |
| Configuration prompts | 10+ |
---
## Production Checklist
Before deploying to production:
- [ ] All tests passing: `php artisan test`
- [ ] Dusk tests passing: `php artisan dusk`
- [ ] Routes verified: `php artisan route:list | grep product`
- [ ] Validation rules complete
- [ ] Form error handling tested
- [ ] Dark mode verified
- [ ] Mobile responsive tested
- [ ] Permissions/authorization added
- [ ] Database migrations fresh: `php artisan migrate`
- [ ] Assets compiled: `npm run build`
- [ ] Error handling tested
- [ ] Delete confirmation working
- [ ] Validation messages clear
- [ ] Performance acceptable
---
## Best Practices
### 1. Plan Your Schema First
```
Take time to plan your columns before running make:rsc:
- Write down all columns you need
- Decide on types and constraints
- Plan relationships with other tables
- Consider indexing strategy
```
### 2. Use Descriptive Names
```bash
# Good: Clear, descriptive names
php artisan make:rsc BlogArticle --label="Blog Articles"
# Avoid: Vague names
php artisan make:rsc Item --label="Items"
```
### 3. Leverage the "back" Feature
```
While adding columns, if you make a mistake:
- Type "back" to remove the last column
- Re-add it with correct settings
- Much faster than deleting and regenerating everything
```
### 4. Use --repository-service-only Wisely
```bash
# Use this when:
php artisan make:rsc Product --repository-service-only
# For API-only resources without views
# For sharing repository logic across multiple controllers
# When you'll create custom controllers
```
### 5. Customize After Generation
```
The generator creates excellent starting points:
1. Generate the full CRUD
2. Test that it works
3. Customize views/validation as needed
4. Don't re-generate if you made small changes
```
### 6. Version Control
```bash
# Commit after successful generation
git add .
git commit -m "feat: create product CRUD"
# This way, if something needs fixing, you can revert
git revert HEAD
```
### 7. Verify Before Deleting
```bash
# Always check what you're about to delete
git status
# The delete command is careful, but verify routes/config removal
grep -r "Product" routes/web.php
grep -r "ProductRepository" app/Providers/
```
---
## Error Recovery
### If Generation Fails
**The generator has built-in rollback:**
1. All generated files are tracked
2. If ANY error occurs, it automatically cleans up
3. Database rolls back if migration fails
4. No orphaned files left behind
```
Error occurred: [details]
Cleaning up generated files...
Deleted: Model
Deleted: Repository
Deleted: Service
Deleted: Controller
...
Generation failed and files have been cleaned up.
```
### Manual Recovery
If you need to fix something:
```bash
# Check what files exist
git status
# View the error in detail
php artisan make:rsc Product --label="Products" 2>&1
# Delete manually if needed
php artisan delete:rsc Product
# Re-run with correct options
php artisan make:rsc Product --label="Products"
```
### Database Recovery
If migration failed:
```bash
# Check table status
php artisan tinker
> Schema::getTables()
# Rollback last migration
php artisan migrate:rollback
# Or reset everything
php artisan migrate:fresh # ⚠️ Deletes all data
```
---
## Files Reference
### Main Commands
```
app/Console/Commands/
├── MakeRepositoryServiceController.php # Generate CRUD
└── DeleteRepositoryServiceController.php # Delete CRUD
```
### Generators
```
app/Console/Commands/Generators/
├── MigrationGenerator.php
├── ModelGenerator.php
├── RepositoryGenerator.php
├── ServiceGenerator.php
├── ControllerGenerator.php
├── FormRequestGenerator.php
├── BladeGenerator.php
├── RouteGenerator.php
└── ServiceProviderBindingGenerator.php
```
### Blade Stubs
```
app/Console/Commands/Stubs/
├── TailwindBladeIndexStubGenerator.php
├── TailwindBladeCreateStubGenerator.php
├── TailwindBladeEditStubGenerator.php
└── TailwindBladeShowStubGenerator.php
```
### Tests
```
tests/Browser/
├── ProductCrudTest.php (example)
└── screenshots/ (auto-generated)
```
---
## Related Documentation
- [Laravel Documentation](https://laravel.com/docs)
- [Tailwind CSS](https://tailwindcss.com/docs)
- [Laravel Dusk](https://laravel.com/docs/dusk)
- [RESTful Routes](https://laravel.com/docs/routing#restful-routes)
---
## Summary
**Tailwind CRUD Generator v2.0** creates professional CRUD applications with:
**Generation Features:**
- ✅ Interactive migration creation with column configuration
- ✅ Automatic column verification
- ✅ Smart input type selection (full enum support with pre-populated select options)
- ✅ Column-aware filter UI (text, date range, enum dropdown) on every index page
- ✅ Repository + Service + Controller generation (filter-aware)
- ✅ Form Request auto-generation
- ✅ Blade view creation (index, create, edit, show)
- ✅ Automatic route registration
- ✅ Service Provider binding
- ✅ Sidebar menu entry appended to `config/sidebar.php`
**Cleanup Features:**
- ✅ Complete file deletion
- ✅ Route removal
- ✅ Service Provider binding removal
- ✅ Sidebar entry removal from `config/sidebar.php`
- ✅ Optional migration cleanup
- ✅ Runs `php artisan optimize` after cleanup
**Design:**
- ✅ Modern Tailwind CSS v4 styling
- ✅ Responsive mobile-first design
- ✅ Dark mode support
- ✅ Configurable view paths
- ✅ RESTful routing
**Testing & Documentation:**
- ✅ Dusk browser tests
- ✅ Auto-generated screenshots
- ✅ Comprehensive documentation
- ✅ Error handling with automatic cleanup
**Status:** ✅ Production Ready
**Last Updated:** July 1, 2026
**Version:** 2.1
**Maintainer:** Laravel Boost Team
---
**Ready to build. Happy CRUDing!** 🚀