How to choose the right module?

There are several things to consider when choosing the right module for your Drupal project.

Like any other open source system, the biggest problem is that in Drupal there are always several ways to get the same result, and therefore it is normal that you can find more than one module for each functionality. This is what you should take into account before choosing which one to use:

Compatibility

Before downloading a module, you should know if it will be compatible with your current version of Drupal.

Assuming that your website is a Drupal 9, then you have to make sure that the module has a Drupal 9 compatible version. Having a version for Drupal 7 or Drupal 8 does not mean that it will work in Drupal 9.

To find out the available versions of the module, you can go to the module project page on Drupal.org and scroll to the bottom, where you will see the download link and find the specified release versions.

They are free but consume space

One thing to keep in mind is that, although Drupal modules contributed by the community are free and you don't pay money for them, they do have a cost for your website.

Unused modules can unnecessarily consume a large amount of space and resources, which can make your website heavier and slower.

So, before downloading a module, it is advisable to analyze if you really need it or if any other main module you already use can perform the same functionality for your website.

Don't hesitate to abandon those inactive and underused modules to make your website healthier and lighter.

Actively maintained modules

It is very important to choose modules that are actively maintained, updated and published by the developers.

Mainly because if security vulnerabilities or any other problems are found, you are likely to get a faster response from the developer/contributor. Plus, you'll have a much better chance that an updated version will arrive soon.

If you are hesitating between two modules and one of them has not been updated for 2 years …. better take the other one.

Popularity

It may seem obvious, but using popular modules generally means that you can trust the module to do the job safely and with fewer problems. On the module's project page on Drupal.org, you can see the number of downloads and how many websites are currently using that particular module.

These are really estimated statistics and not exact numbers, but they serve as a fact to keep in mind.

If you have to choose between a module with 100 downloads or one with 10,000 downloads, surely the 10k module is a more polished module, which works better and has more community support to solve possible issues.

Attention to issues

The issues are the reports made by the community of the things that seem not to work well with this module.

On the module project page, on the right side, you can find the number of issues and bugs (open and closed) associated with that module. By clicking on the link, you will be shown a detailed report of all bugs and issues that will help you get an idea if the module will provide the functionality you are looking for.

The "Last updated" date can also give you an idea of how responsive the developers are to solving problems.

Versions (Stable, DEV, Beta, Alpha)

By logic, it is better to use the stable version than a version in development, Beta or Alpha. It is logical, but I wanted to emphasize it.

If the module you want to use does not have a stable version, you should be cautious in its use.

You should also keep in mind that NON-stable versions may have many changes between versions, or may contain unresolved issues that can negatively affect your project.

Green shield

Green colored versions with a shield mean that they are covered by the "Drupal Security Team".

In short, it means that the code has been reviewed, that it follows security standards and that if there is a security problem, it will be resolved as quickly as possible.

For example, this module fulfills this requirement: https://www.drupal.org/project/pathauto

Conclusions

When in doubt between two or more modules that do the same thing, you have to look:

1. That it is compatible with your version of Drupal
2. That it has a stable version and not just a DEV version
3. That the stable version is green with a shield
4. The more people using it the better
5. That the last update date is not too old
6. That it has support for the issues

The module with the most points from this list is the winner.