> 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/showcase/sections/main-blog.md).

# Blog

The blog landing page: a 3-column grid of article cards — image, title, and publish date — showing 12 posts per page with pagination. Clicking a card opens the [article page](/sitesbyseth-docs/showcase/sections/main-article.md).

This section has **no settings** — it inherits your global colors, typography, and grid gap. Manage the posts themselves under **Online Store → Blog posts** in your Shopify admin, and link the blog into your menu via **Online Store → Navigation**.

💡 Every post's card leans on its **featured image** — posts without one show as text-only cards. Set a featured image on each post and keep the crops consistent for a clean grid.


---

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