Drupal Blocks and Block Types

Reusable custom block types are defined in code as plugins rather than stored as UUID-specific content blocks. This approach ensures portability across environments, consistent naming, and maintainability. Code-based definitions let you version control your block structure and redeploy it reliably.

Machine names for blocks should be concise and generic, avoiding region-specific prefixes or 'block_' prefixes. Use descriptive names like 'cta' or 'testimonial' that reflect the block's purpose and remain consistent across environments for easier deployment and reuse.

Apply the same content modeling standards used for nodes and paragraphs to your block fields and view modes. Align field types, naming, and view mode configurations with your broader content architecture to maintain consistency and reduce cognitive overhead across your site.

Document caching requirements for each block type based on its content freshness needs and reusability scope. Proper cache tags and contexts ensure blocks display current data while maximizing performance benefits across your site's environments.

Code-based block plugins are designed for portability across environments. UUID-specific content blocks are environment-dependent and difficult to redeploy, so block type plugins are the recommended approach for maintainable, reusable site architecture.