> For the complete documentation index, see [llms.txt](https://bigstart.gitbook.io/amber-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bigstart.gitbook.io/amber-documentation/pages/blog.md).

# Blog

This is the main template/page where your blog articles are listed. You can manage your blog by going to `Online store > Blog posts`.

The blog template of Amber consists of 2 main sections:

* Image with text overlay
* Main blog

### Image with text overlay

More information about this section can be found [here](/amber-documentation/content-sections/image-with-text-overlay.md).

### Main blog

This is the main section that prints articles in your site.

You can enable/disable the category filters above the articles by checking the `Enable filters` checkbox.\
The filters are based on the article tags.

The articles show their featured images, tags, excerpt, title and author.\
For the `3 min read` label, you can add a prefixed tag to the article, for example `read_time: 3`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://bigstart.gitbook.io/amber-documentation/pages/blog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
