Develop
- Local server setup
- Development tools
- Using Composer
- Git version control system
- Managing a drupal.org theme, module, or distribution project
- Security
- Drupal project issues
- Usability testing
- Profiling Drupal
- [Obsolete] Coding standards
- User interface standards
- Theming Drupal
- Creating custom modules
- Drupal APIs
- Automated Testing
- Upgrading and converting Drupal 7 modules
- Core modules and themes
- External Libraries in Core
- Mobile guide
- Decoupled Drupal
[Obsolete] Coding standards
The standards have moved to Drupal coding standards.
The Drupal coding standards apply to code within Drupal and its contributed modules. These standards are version-independent and "always-current".
All new code should follow the current standards, regardless of (core) version.
Existing code in older versions may be updated. For large code-bases (like Drupal core), updating the code of a previous version for the current standards may be too huge of a task.
Comments and names should use US English spelling.
Coding standard fixes are done by rule not individual files.
The video tutorial, Understanding the Drupal Coding Standards, explains the standards, why they are important, and how to use them.
[Obsolete] PHP
PHP coding standards.
[Obsolete] CSS
CSS coding standards and best practices.
[Obsolete] JavaScript coding standards
JavaScript coding standards and best practices for Drupal.
[Obsolete] Markdown
This is currently being discussed.
[Obsolete] SQL
SQL best practices for Drupal.
[Obsolete] Twig coding standards
Drupal project standards regarding Twig coding
[Obsolete] Drupal Markup Style Guide
Standards related to HTML and CSS markup
[Obsolete] Spelling
The spelling standard for all Drupal code.
[Obsolete] YAML Configuration files
Configuration file standards
[Obsolete] Composer package naming conventions
A collection of not only the basics behind Drupal's naming convention for Composer packages but also some more advanced cases good to know.