Laravel 11 Slim Skeleton: Guide to New Minimalist Structure

Laravel 11 is Here: Mastering the New "Slim Skeleton" and Minimalist Structure

The release of Laravel 11 marks a significant shift in how developers interact with the framework. With a focus on simplicity and efficiency, the new "Slim Skeleton" reduces boilerplate code and offers a more minimalist starting point. This update streamlines the development process, allowing you to focus more on building features and less on managing configuration files.

Understanding the Core Directory Changes

The most visible change in Laravel 11 is the reduction of files and directories in a fresh installation. The goal is to declutter the workspace while maintaining the powerful flexibility Laravel is known for. The app directory has been significantly simplified.

The Streamlined App Directory

Gone are the days of an overcrowded application folder. In Laravel 11, the app/Console, app/Exceptions, and app/Http/Middleware directories have been removed. Their functionality has not disappeared but has been moved to a more central location to keep your project structure clean.

?

Centralized Configuration in Bootstrap

A major shift involves the  bootstrap/app.php file. This file now acts as the control center for your application. You can now configure routing, middleware, exception handling, and service providers directly in this file. This reduces the need to jump between multiple files to make simple global changes.

Key Structural Differences: Laravel 10 vs. Laravel 11

To help you visualize the changes, here is a quick comparison of the default structure between the previous version and the new minimalist approach.

Adapting to the New Configuration Workflow

In previous versions, the config folder was packed with files for every service. Laravel 11 takes a different approach. Most configuration files are now hidden by default, relying on sensible internal defaults. If you need to customize a specific setting, you can publish the configuration file using the comman

This command allows you to selectively bring configuration files into your project only when you actually need to modify them. This keeps your project folder clean and easy to navigate.

API and Broadcasting are Now Opt-In

Many modern web applications are purely monolithic or do not require complex API structures initially. Recognizing this, Laravel 11 does not include api.php or channels.php route files by default. If your project requires these features, you can easily install them using Artisan commands.

Running php artisan install:api will set up the API routes file and install Laravel Sanctum for authentication. Similarly, broadcasting support can be added when needed.

Common Questions About Laravel 11

Q: Will my existing Laravel 10 application break if I upgrade?

A: No, the new structure is for fresh installations. Upgraded applications will retain their existing directory structure, so you do not need to manually move files around.

Q: Where do I register my custom middleware now?

A: You register middleware in the bootstrap/app.php file. There is a dedicated method for configuring global and group middleware without needing a separate Kernel file.

Q: Can I still use MySQL instead of SQLite?

A: Absolutely. SQLite is just the default for new projects to speed up local development. You can change your database connection in the .env file just like before.

Q: What happened to the Console Kernel?

A: The Console Kernel has been removed. You can now define your schedule and commands directly in the  routes/console.php file using the new streamlined syntax.

Q: Is the new structure mandatory for all projects?

A: It is the standard for new projects, but Laravel is flexible. You can manually create the old folders if you prefer, though adapting to the new minimalist style is recommended for future compatibility.