🚀 Introduction

Drupal 11.3.0 brings a powerful update for themers and front-end developers:
themes can now implement hooks using Object-Oriented Programming (OOP) with the #[Hook()] attribute — just like modules have been able to do since Drupal 11.

This means no more long procedural functions in template.php.
Instead, you can organize your logic cleanly in classes inside the theme’s src/Hook directory.

🔄 Updating hook_help() When Migrating from Drupal 8 to Drupal 11.2

With the release of Drupal 11.2, developers are encouraged to modernize their codebase by replacing legacy hooks with more structured, object-oriented alternatives. One of the most commonly used hooks in legacy modules is hook_help() — the function that adds helpful module documentation to the /admin/help page.

Hooks in both WordPress and Drupal 8 are mechanisms for developers to extend and modify the functionality of the core software or themes/modules without modifying the original code directly. However, their implementation differs between the two platforms.

WordPress Hooks:

In WordPress, hooks are actions and filters.

Filter Hooks in WordPress:
- Filter hooks are used to modify data or the result of an operation before it's outputted or used in WordPress.
- They allow for modifying text, metadata, attributes, and other data that WordPress generates or retrieves before it's displayed.
- Example: the_content, the_title, the_excerpt.

Hooks in WordPress and Drupal provide similar functionality, allowing developers to interact with the system and modify its behavior without changing the core code.

Here are the main differences between hooks in WordPress and Drupal: