<p>Modules extend your site functionality beyond Drupal core.</p>

<h2>WHAT TO PLACE IN THIS DIRECTORY?</h2>

<p>Placing downloaded and custom modules in this directory separates downloaded and
custom modules from Drupal core&#39;s modules. This allows Drupal core to be updated
without overwriting these files.</p>

<h2>DOWNLOAD ADDITIONAL MODULES</h2>

<p>Contributed modules from the Drupal community may be downloaded at
<a href="https://www.drupal.org/project/project_module" rel="nofollow">https://www.drupal.org/project/project_module</a>.</p>

<h2>ORGANIZING MODULES IN THIS DIRECTORY</h2>

<p>You may create subdirectories in this directory, to organize your added modules,
without breaking the site. Some common subdirectories include &#34;contrib&#34; for
contributed modules, and &#34;custom&#34; for custom modules. Note that if you move a
module to a subdirectory after it has been enabled, you may need to clear the
Drupal cache so it can be found.</p>

<p>There are number of directories that are ignored when looking for modules. These
are &#39;src&#39;, &#39;lib&#39;, &#39;vendor&#39;, &#39;assets&#39;, &#39;css&#39;, &#39;files&#39;, &#39;images&#39;, &#39;js&#39;, &#39;misc&#39;,
&#39;templates&#39;, &#39;includes&#39;, &#39;fixtures&#39; and &#39;Drupal&#39;.</p>

<h2>MULTISITE CONFIGURATION</h2>

<p>In multisite configurations, modules found in this directory are available to
all sites. You may also put modules in the sites/all/modules directory, and the
versions in sites/all/modules will take precedence over versions of the same
module that are here. Alternatively, the sites/your_site_name/modules directory
pattern may be used to restrict modules to a specific site instance.</p>

<h2>MORE INFORMATION</h2>

<p>Refer to the “Developing for Drupal” section of the README.txt in the Drupal
root directory for further information on extending Drupal with custom modules.</p>