# Snippets

{% hint style="warning" %}
The Snippets feature is no longer maintained in GitBook and is subject to change. We recommend to structure your content a [space](/docs/creating-content/content-structure/space.md) instead.
{% endhint %}

Snippet blocks are a great way to reference a snippet in your content. Snippet blocks help make the link to your snippet stand out on the page compared to [an inline link](/docs/creating-content/formatting/inline.md#relative-links).

You can only use snippet blocks for internal pages. If you add a snippet block to a page in a published space, the public documentation will show the block as a broken link.

{% hint style="warning" %}
**Note:** If you use a snippet block, but then [convert your snippet into a page](/docs/snippets/snippets-beta.md#convert-a-snippet-to-a-page) in your documentation, your snippet block will still link back to the original snippet, which will be archived.
{% endhint %}

### Representation in Markdown

```
{% content-ref url="./" %} . {% endcontent-ref %}
```


---

# 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://gitbook.com/docs/creating-content/blocks/snippets.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.