By creating classes in the tasks directory, you are able to add your own custom tasks to the
Laravel Artisan command line interface. Tasks are represented by classes and methods.
/tests
The tests directory provides a location for you to keep your application unit tests. If you are
using PHPUnit, you can execute all tests at once using the Laravel Artisan PHP command line
interface.
/views
The views directory contains your HTML template files to be used by controllers or routes,
although please use a .php extension for files in this directory. You can alternatively use a
.blade.php extension to enable parsing with the Blade templating library which will be explained
in a later chapter.
/bundles.php [file]
To enable a bundle, simply add it to the array in bundles.php. You can also use a key-value,
name-array pair to define extra options for the bundle.
/routes.php [file]
The routes file contains the methods which enable routes to be mapped to their appropriate
outcome with Laravel. This topic will be explained more thoroughly in upcoming chapters.
This file also contains declarations for several events including error pages, and can be used to
define view composers or route filters.
/start.php [file]
The start.php contains start-up routines for the /application bundle, such as auto-loading
directories, loading configuration files, and other wonderful useful stuff! Feel free to append
to this file.
In the next chapter we will be cover routing using controllers.