# Annotations 🧪

{% hint style="danger" %}
**CONCEPTUAL**\
This is a feature set we're considering.
{% endhint %}

## Conceptual Examples

* Hint blocks, such as an info, warning, feature etc.
* Tooltips
* Footnotes
* Buttons

Embedded content? ;

* Tables
  * From Google docs / Google sheets
* Other content
  * Google sheets content 
* Figma
* Diagrams 

## Markup

The goal is to use markup within the Rich Text Block editor that is memorable, easily applied, and will not conflict with Webflow's native markdown detection support.

Line items

Indication is places at the start of the line

* e.g. >> 
* e.g. @ 
* e.g. @@ 
* e.g. = 
* e.g. == 

List items

Within lists, these start-of-line indicators are similar, but can have different meanings

* e.g.

Blockquote annotations

Within blockquotes, these can be used at the start of the blockquote to create a note / hint block

* e.g. ! Alert
* e.g. ? warning
* e.g. # note
* e.g. \~ deprecation note

These should be interpreted, removed, and a class applied. That class should then affect the styling, coloring, and iconography of the blockquote, and be designed on a style guide page. 

Inline items

* e.g. Footnotes \[1]  
* \[\[ ]]
* {{ }}
* \~\~ strikethrough text 


---

# 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://attr.sygnal.com/sa5-richtext/annotations.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.