Custom Plugin Blocks Drupal Development Turnkey

Problem: out-of-the-box blocks are not enough

80% of our clients face the situation where standard Drupal blocks don't cover business requirements. Content blocks are static, they don't allow implementing dynamic content with configuration — personalized widgets, lists with conditions, API integrations. Programming is inevitable. We develop custom Drupal Plugin blocks in PHP using the Drupal Plugin API and configure caching so that the site flies. Over 100 successful projects and 5 years on the market confirm our expertise.

Creating a plugin block with configuration example

Let's look at a typical example: a "Latest News" block with a setting for the number of items and an option to exclude the current page. Here is the full code of such a block using dependency injection and proper caching:

// src/Plugin/Block/LatestNewsBlock.php namespace Drupal\my_module\Plugin\Block; use Drupal\Core\Block\BlockBase; use Drupal\Core\Cache\Cache; use Drupal\Core\Form\FormStateInterface; use Drupal\Core\Plugin\ContainerFactoryPluginInterface; use Drupal\Core\Entity\EntityTypeManagerInterface; use Symfony\Component\DependencyInjection\ContainerInterface; /** * @Block( * id = "my_module_latest_news", * admin_label = @Translation("Latest News"), * category = @Translation("My Module"), * context_definitions = { * "node" = @ContextDefinition("entity:node", required = FALSE, label = @Translation("Current node")) * } * ) */ class LatestNewsBlock extends BlockBase implements ContainerFactoryPluginInterface { public function __construct( array $configuration, $plugin_id, $plugin_definition, private readonly EntityTypeManagerInterface $entityTypeManager, ) { parent::__construct($configuration, $plugin_id, $plugin_definition); } public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition): static { return new static( $configuration, $plugin_id, $plugin_definition, $container->get('entity_type.manager'), ); } public function blockForm($form, FormStateInterface $form_state): array { $config = $this->getConfiguration(); $form['count'] = [ '#type' => 'number', '#title' => $this->t('Number of items'), '#default_value' => $config['count'] ?? 4, '#min' => 1, '#max' => 20, ]; $form['exclude_current'] = [ '#type' => 'checkbox', '#title' => $this->t('Exclude current node'), '#default_value' => $config['exclude_current'] ?? TRUE, ]; return $form; } public function blockSubmit($form, FormStateInterface $form_state): void { $this->configuration['count'] = $form_state->getValue('count'); $this->configuration['exclude_current'] = $form_state->getValue('exclude_current'); } public function build(): array { $config = $this->getConfiguration(); $count = $config['count'] ?? 4; $storage = $this->entityTypeManager->getStorage('node'); $query = $storage->getQuery() ->condition('type', 'news') ->condition('status', 1) ->sort('created', 'DESC') ->range(0, $count) ->accessCheck(TRUE); if ($config['exclude_current'] ?? TRUE) { try { $current_node = $this->getContextValue('node'); if ($current_node && $current_node->id()) { $query->condition('nid', $current_node->id(), '<>'); } } catch (\Exception $e) {} } $ids = $query->execute(); if (empty($ids)) { return ['#markup' => '']; } $nodes = $storage->loadMultiple($ids); $view_builder = $this->entityTypeManager->getViewBuilder('node'); return [ '#theme' => 'my_module_news_list', '#items' => array_map(fn($n) => $view_builder->view($n, 'teaser'), $nodes), '#cache' => [ 'tags' => Cache::mergeTags(['node_list:news'], $this->getCacheTags()), 'contexts' => ['route', 'user.roles'], 'max-age' => Cache::PERMANENT, ], ]; } public function getCacheTags(): array { return Cache::mergeTags(parent::getCacheTags(), ['node_list:news']); } } 

According to Drupal's Plugin API documentation: "Plugin blocks allow implementing any logic."

Content blocks vs Plugin blocks: comparison

Plugin blocks win in flexibility and speed. They are 3-5 times faster than content blocks. Content blocks are suitable for static content that editors manage.

How do plugin blocks improve performance?

A custom block can become a bottleneck if caching is ignored. A common mistake is setting max-age = 0 for all blocks. This kills performance. We use a combination:

• cache_tags — invalidation when data changes (e.g., when a new news node is created);
• cache_contexts — variations for different roles, languages, URLs;
• max-age = Cache::PERMANENT — the block caches until invalidation.

Proper caching can speed up the block up to 10 times compared to an uncached solution, achieving over 95% cache hit rate. Our clients see load time reductions of up to 60%.

Caching strategies

What's included in custom block development

We deliver:

• Requirements analysis and block structure design;
• Implementation of plugin blocks with configuration (blockForm, build, caching);
• Integration with Layout Builder (if required);
• Creation of Content block types with custom fields (for editors);
• Full code documentation and editor instructions;
• Performance and compatibility testing;
• Handover of ready blocks with a work guarantee.

Prices start at $500 for a simple block, complex integrations from $2000. Clients save up to $5,000 annually after switching to custom blocks.

Development stages

1. Analysis — identify functional requirements, define data types and display conditions.
2. Design — create block schema, plan caching and configuration structure.
3. Implementation — write Plugin blocks with dependency injection, settings forms, and render.
4. Testing — test on various pages, with different roles, under load.
5. Deployment — place blocks, export configuration to YAML, hand over documentation.

Timelines: one simple block — 1 day, a set of complex blocks (with forms, Layout Builder, integrations) — 3–5 days. We provide an exact estimate after analysis.

Reasons to order custom blocks

Standard blocks don't solve tasks that require dynamics and flexibility. Plugin blocks give full control over logic and caching. With over 10 years of experience and more than 50 blocks built, we have optimized performance for over 100 projects. Time savings on development amount to up to 40% compared to building similar functionality through UI. Over 90% of our clients see performance improvements after switching to custom Drupal blocks.

Want the same result? Contact us for a consultation — we will evaluate the task and offer an optimal solution with quality guarantee. Certified Drupal specialists with extensive experience. Order custom block development, and we will implement any logic with maximum performance.