# HTML

### Key Features

* **User Status**: The template adapts based on the user's logged-in status.
* **Dynamic Root Path**: It identifies and classifies pages based on their root path (e.g., 'node', 'admin', 'user').
* **Content Type Recognition**: For pages representing a node, the template can identify the content type.
* **Flexible Head Title**: Comprises elements like page title, site name, and slogan, assembled dynamically.
* **Page Segmentation**: Divides the page into `page_top`, `page`, and `page_bottom` segments for structured content rendering.
* **Offline Database Flag**: Indicates if the database is offline.
* **Head, CSS, and JS Management**: Integrates placeholders for head elements, CSS, and JavaScript.
* **Accessibility Features**: Includes a 'Skip to main content' link for enhanced keyboard navigation.

### Customization

* **CSS and JS Integration**: Easily integrate custom stylesheets and JavaScript files using placeholders.
* **Language and Path-based Styling**: Customize the appearance based on language settings and the root path.

### Usage

```twig
{% embed "radix:html" with {
  attributes: { class: ['custom-class'], id: 'custom-page-id' },
  logged_in: true,
  root_path: 'node',
  node_type: 'article',
  head_title: { title: 'Example Radix Page', name: 'Yolo!', slogan: 'Yolo today!' },
} %}
  {% block body_end %}
    'Some JS code that needs to run at the end of the body tag'
  {% endblock %}
{% endembed %}
```


---

# 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/html.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.