How to read this guide
Although this guide is not a standard, using the most of suggested ideas will make your Drupal site more organised and easy to manage.
The guide covers organisation of files in project, files in module, functions in files, hooks implementations, features organisation and other development tricks.
It also covers interaction with git, continuous integration and code linting.
- All project code MUST comply with Drupal coding standards.
- All project documentation MUST comply with API documentation and comment standards.
The following placeholders are used throughout code examples:
MYMODULEGeneric module name that should be replaced with your own module name. Usually used in hook implementation examples.
projectshortnameProject name abbreviation. Usually used as a prefix for custom modules.
Please refer to RFC2119 for meaning of words
All donations are forwarded to Drupal Association.