Building Custom Drupal 10 Modules: A Complete Guide

Why Custom Modules?

While Drupal's contributed module ecosystem is vast, enterprise projects almost always need custom functionality. Whether it's a unique content workflow, a proprietary API integration, or business logic specific to your domain — custom modules are how Drupal developers extend the platform.

Module Scaffolding

Every Drupal module starts with a .info.yml file. This declares your module's metadata, dependencies, and compatibility:

name: 'My Custom Module'
type: module
description: 'Provides custom functionality for the platform.'
core_version_requirement: ^10
package: Custom
dependencies:
  - drupal:node
  - drupal:user

Services and Dependency Injection

Modern Drupal development leans heavily on Symfony's service container. Define your services in my_module.services.yml:

services:
  my_module.content_manager:
    class: Drupal\my_module\Service\ContentManager
    arguments: ['@entity_type.manager', '@current_user', '@logger.factory']

This approach gives you testable, decoupled code. Each service declares its dependencies explicitly, making the architecture transparent.

Hook Implementations

Hooks remain a fundamental extension mechanism in Drupal. The most commonly used hooks include hook_form_alter() for modifying forms, hook_entity_presave() for intercepting entity operations, and hook_theme() for registering theme hooks.

function my_module_form_alter(&$form, FormStateInterface $form_state, $form_id) {
  if ($form_id === 'node_article_form') {
    $form['field_category']['#access'] = \Drupal::currentUser()->hasPermission('edit article category');
  }
}

The Plugin API

Drupal's Plugin API is one of its most powerful features. It allows you to define swappable, discoverable components. Common plugin types include Blocks, Field Formatters, and REST Resources.

Creating a custom plugin type involves defining a plugin manager, an interface, and an annotation or attribute class. This architecture enables other modules to extend your functionality without modifying your code.

Best Practices

• Follow Drupal coding standards: Use phpcs with the Drupal standard
• Write tests: PHPUnit for unit tests, Kernel tests for integration
• Use dependency injection: Avoid static calls to \Drupal::service()
• Cache appropriately: Tag your caches for proper invalidation
• Document your code: phpDoc blocks on all public methods

Conclusion

Building custom Drupal modules is where backend development gets interesting. The combination of hooks, services, plugins, and events gives you a powerful toolkit for extending Drupal in any direction your project requires.