> For the complete documentation index, see [llms.txt](https://bigstart.gitbook.io/marble-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/marble-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 Marble consists of 2 main sections:

* Blog Banner
* Main blog

You can add more sections to this page by using the `Add section` button below the sections here:

<figure><img src="/files/eyeyoMdt3j5JKrVgDgO0" alt=""><figcaption></figcaption></figure>

More details about the 2 sections below.

## Blog Banner

The main purpose of this section is to present a good looking banner above the articles. The blog title is automatically loaded from the blog. The other details like image, etc. are set through the section settings.

## Blog Main

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

Here are the settings available for this section.

* Style - more details [here](/marble-documentation/content-sections/common-settings.md#style)
* Show author
* Show date
* Show excerpt
* Show tags


---

# 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/marble-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.