Now Laravel Developer will experience new design which has already covered the fresh routes directory and a latest directory change coming many of the default folders will not show up until you run a command that needs them.

1. Directory Structure
Changes in Laravel 5.3

2. • Laravel is continuously updating its newest versions
and some changes that will change the directory
structure
• A latest directory change coming many of the default
folders will not show up until you run a command that
needs them
• Each version of Laravel have its directory prior to 5.3
but usually not used

3. • List of folders that are going away:
– L i s t e n e r s
– E v e n t s
– J o b s
– P o l i c i e s
• These are directories that hold a single, more forward
class structure that aren’t global to Laravel apps.
Events, Jobs, Listeners, and Policies

4. What Is The Models Directory?
• Lots of developers are in a fix by the lack of a models
directory
• The lack of such a directory is mandatory
• the word “models” ambiguous since it means
different to many people
– as the collectively of all of its business logic
– as classes that reach out with a relational database

6. • The App Directory - App directory contains the main code for
any application. Almost all of the classes in your app will be in
the directory.
• The Bootstrap Directory - This directory contains files that load
the framework and compose auto loading. This directory also
builds a cache directory which holds framework generated files
for functionality development such as the route and services
cache files.

7. • The Config Directory - The config directory, as the name
implies, holds all of your application’s configuration files.
• The Database Directory - This directory comprises your
database migration and seeds. Developers may also use this
directory to grip a SQLite database.
• The Public Directory - This directory contains the index.php
file, which is the initial point for all requests arriving in your
application and also houses your assets such as images,
JavaScript, and CSS.

8. • The Storage Directory - Storage directory holds your compiled
Blade templates, sessions, caches, and other files developed by
the framework.
• The Tests Directory - This directory holds your computerized
tests. Each test class should be suffixed with the word Test. You
may run your tests using the phpunit or php
vendor/bin/phpunit commands.