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

# Blog

The blog index: a grid of your posts — cover image, title, and publish date — 3 columns on desktop, 1 on mobile, 12 posts per page with pagination.

**Where to find it:** theme editor → page selector → **Blogs → Blog**. Write posts under **Online Store → Blog posts** in your admin.

## Settings

### Section style

* **Top padding** / **Bottom padding** (0–120 px, default 64), **Background color**, **Text color**.

That's everything — the grid itself is automatic.

💡 **Pro tip:** posts without a featured image render as text-only cards in the grid, which looks unbalanced next to image cards — set a featured image on every post, ideally all in the same aspect ratio. For a streetwear brand, the blog works hardest as a drop archive: one post per drop with the campaign shots and the story.


---

# 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://sitesbyseth.gitbook.io/sitesbyseth-docs/skeleton/sections/main-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.