sis.modules

When a module is added to a view, some configuration might be required. The configuration can be stored in the database as key, value. Even if some keys need multiple values we could serialize the values. When a module is implemented, two views are necessary. A view where the data is displayed and one where the configuration is set. This way each module has it’s own configuration view.

In terms of the data source we would like to avoid making multiple calls from different modules for the same data. This could be achieved by having an application-wide data dispatcher and each module would subscribe to it.