Mercurial > hg > isophonics-drupal-site

annotate modules/README.txt @ 19:fa3358dc1485 tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add ndrum files
author Chris Cannam
date Wed, 28 Aug 2019 13:14:47 +0100
parents 4c8ae668cc8c
children
rev   line source
Chris@0 1 Modules extend your site functionality beyond Drupal core.
Chris@0 2
Chris@0 3 WHAT TO PLACE IN THIS DIRECTORY?
Chris@0 4 --------------------------------
Chris@0 5
Chris@0 6 Placing downloaded and custom modules in this directory separates downloaded and
Chris@0 7 custom modules from Drupal core's modules. This allows Drupal core to be updated
Chris@0 8 without overwriting these files.
Chris@0 9
Chris@0 10 DOWNLOAD ADDITIONAL MODULES
Chris@0 11 ---------------------------
Chris@0 12
Chris@0 13 Contributed modules from the Drupal community may be downloaded at
Chris@0 14 https://www.drupal.org/project/project_module.
Chris@0 15
Chris@0 16 ORGANIZING MODULES IN THIS DIRECTORY
Chris@0 17 ------------------------------------
Chris@0 18
Chris@0 19 You may create subdirectories in this directory, to organize your added modules,
Chris@0 20 without breaking the site. Some common subdirectories include "contrib" for
Chris@0 21 contributed modules, and "custom" for custom modules. Note that if you move a
Chris@0 22 module to a subdirectory after it has been enabled, you may need to clear the
Chris@0 23 Drupal cache so it can be found.
Chris@0 24
Chris@0 25 There are number of directories that are ignored when looking for modules. These
Chris@0 26 are 'src', 'lib', 'vendor', 'assets', 'css', 'files', 'images', 'js', 'misc',
Chris@0 27 'templates', 'includes', 'fixtures' and 'Drupal'.
Chris@0 28
Chris@0 29 MULTISITE CONFIGURATION
Chris@0 30 -----------------------
Chris@0 31
Chris@0 32 In multisite configurations, modules found in this directory are available to
Chris@0 33 all sites. You may also put modules in the sites/all/modules directory, and the
Chris@0 34 versions in sites/all/modules will take precedence over versions of the same
Chris@0 35 module that are here. Alternatively, the sites/your_site_name/modules directory
Chris@0 36 pattern may be used to restrict modules to a specific site instance.
Chris@0 37
Chris@0 38 MORE INFORMATION
Chris@0 39 ----------------
Chris@0 40
Chris@0 41 Refer to the “Developing for Drupal” section of the README.txt in the Drupal
Chris@0 42 root directory for further information on extending Drupal with custom modules.