Creating a Dream Board / Vision Board

[eluser]Vheissu[/eluser]
Modular Extensions is for breaking your code up into modules. Each site action could be a module, although it's not required you'll find using modules means you can take modules from your project and put them into future projects. Prime example of where modules really shine is a pages module for a CMS responsible for loading pages.

If you're building a site down the track that requires similar functionality, you copy and paste the module and it just works provided you also ported any associated database tables or dependencies outside of the module.

Another example is an auth module. Down the track you can copy and paste the auth module into another project and use it. A module is basically a self contained application inside of your main application, so you can have module specific routes, controllers, libraries, configs, models and views.

Just a personal preference, but a great way to ensure code usability and makes your project cleaner. Pyrocms by Phil Sturgeon uses modules, perhaps take a look at why he uses them to see the advantage of modules.

Basically modules aren't required, but they will make your life way easier.