I have already mentioned modules several times, for example, the Issue tracking module that we discussed in the previous chapter. Thence, you have probably concluded that a module is a part of a functionality, and that's correct. But to be more precise, this is a part of the functionality that is used for projects. This is why Redmine modules are also often called project modules.
Actually, modules are like bricks, with which you can build a website for your project. On the other hand, they can also be used to disable functionality that is not needed. But generally, modules are nothing more than virtual units, as they are not plugins, their files are not stored separately from the core, and so on.
Certainly modules can also be provided by plugins, but we are going to discuss only core project modules here. Even so, not all of them will be reviewed in this chapter. Thus, as we have discussed the Issue tracking module in the previous chapter, we will skip it here. However, we will review...