Why this lesson matters
Understand project structure and apply it in a small Laravel feature. Laravel conventions connect Composer, Artisan, environment configuration and the application directory into one predictable runtime.
How to reason about it
- For Project Structure, the outcome to verify is: Map each directory to its responsibility before adding application logic.
- In Project Structure, keep this failure controlled: Do not start copying framework code before you can explain where routes, configuration, application classes and tests live.
- Project Structure practice target: Inspect a fresh project and trace one request from the route list to the file that would handle it.
Project layers
Routes
Practical walkthrough
In the Project Structure walkthrough: Map each directory to its responsibility before adding application logic.
structure.txttext
app/Http/Controllers
routes/web.php
routes/api.php
resources/views
database/migrations
tests/FeaturePractice it yourself
Project Structure exercise
Inspect a fresh project and trace one request from the route list to the file that would handle it.
- Record the expected result before execution
- Test one valid path and one lesson-specific failure path
- Explain in two lines which boundary owns the decision
