> For the complete documentation index, see [llms.txt](https://docs.mburger.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mburger.cloud/sample-app-1/create-home-news-and-gallery-blocks.md).

# Create Home, News and Gallery blocks

From the **settings** tab create a new block called **Home** with the following elements:

* A *title* (type `text`) with name “title”
* An *image gallery* (type `image`) with name “image”
* A *description* (type `textarea`) with name “description”

Then, repeat this for the **News** block with pretty much the same data. 

Repeat this as well for the **Gallery** block with the same data but leaving out the description. 

{% hint style="info" %}
Take note of the names of the fields and create some content by entering each created block and clicking **Add Section**

Take note of the id of each block inside the settings of each block, let’s call them `HOME_BLOCK_ID`, `NEWS_BLOCK_ID` and `GALLERY_BLOCK_ID`
{% endhint %}


---

# 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://docs.mburger.cloud/sample-app-1/create-home-news-and-gallery-blocks.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.