In the previous chapter, we touched upon the fact that packages don't relate directly to a URL; they need controllers and views in the application to do this. Modules, on the other hand, are a group of MVC elements that can act independently from the project application. They allow for the encapsulation and reusability of your code, so that you can share a module between projects without needing to write an application code to fully utilize the functionality.
Modules are expected to reside within the modules folder within the application. If you would prefer to store them elsewhere, this path and folder can be changed in the application configuration. It's recommended to use modules on larger projects that consist of a large code base as they can help keep the code in order.
Modules can be used independently and they don't need access to the global application code. A route can be created to allow for a module to be directly accessed via a URL. Since modules...