# Block

### Features

* **Dynamic Layout**: The template supports different layouts, which can be specified using the `layout` variable.
* **Customization**: You can customize the block by setting various configuration values, such as `label`, `label_display`, and `provider`.
* **Unique Identification**: Each block comes with a unique `id`, ensuring no conflicts in the HTML document.
* **HTML Attributes**: The template supports adding custom HTML attributes to the main container, title, and content tags.
* **Custom Class Handling**: It utilizes the `block_classes` set for applying CSS classes based on the block's configuration and plugin ID.
* **Content Rendering**: The content of the block is rendered within a designated area, with the ability to add custom attributes and classes.
* **Label Handling**: The block's label is managed with flexibility, allowing for inclusion only if specified.
* **HTML Tag Customization**: The HTML tag for the block can be defined, offering further control over the block's markup.

### Template Structure

The template is structured into several sections, each handling different aspects of the block:

* **Block Container**: Defined by `html_tag`, it wraps the entire block.
* **Title Prefix and Suffix**: Allows for additional content before and after the main title.
* **Block Label**: Managed within its block for conditional rendering.
* **Block Content**: A dedicated section for the main content of the block.

### Usage

```twig
{% include 'radix:block' with {
  html_tag: 'div',
  block_utility_classes: [
    'some-utility-class',
  ],
} %}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.trydrupal.com/radix/components/block.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.