# Basics
* [Interpolation](#interpolation)
* [Attributes](#attributes)
* [Attribute Values](#attribute-values)
* [Quoted Attribute Names](#quoted-attribute-names)
* [Unescaped Attributes](#unescaped-attributes)
Jael syntax is a superset of HTML. The following is valid both in HTML and Jael:
```markup
Title
Hello!
```
However, Jael adds two major changes.
## Interpolation
Firstly, text blocks can contain *interpolations*, which are merely Dart expression contained in double curly braces (`{{ }}`). The value within the braces, once evaluated will be HTML escaped, to prevent XSS. To achieve unescaped output, append a hyphen (`-`) to the first brace (`{{- }}`).
```markup
{{ user.name }}
{{- raw.data.will.not.be('escaped') }}
```
## Attributes
Secondly, whereas in HTML, the values of attributes can only be strings, Jael allows for their values to be any Dart expression:
```markup
Link
```
### Attribute Values
Values are handled as such:
* Maps: Serialized as though they were `style` attributes.
* Iterables: Joined by a space, like `class` attributes.
* Anything else: `toString()` is invoked.
### Quoted Attribute Names
In case the name of your attribute is not a valid Dart identifier, you can wrap it with quotes, and it will still be processed as per normal:
```markup
```
### Unescaped Attributes
These will also be HTML escaped; however, you can replace `=` with `!=` to print unescaped text:
```markup
```
---
# 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.angel-dart.dev/1.x/front-end/jael/basics.md?ask=
```
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.