> 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-article.md).

# Article

A single blog post: a breadcrumb back to the blog, the title, the publish date, the featured image (in the theme's 1px border), and your content at a comfortable 800px reading width.

**Where to find it:** theme editor → page selector → **Blogs → Article**. The content itself is written under **Online Store → Blog posts**.

## Settings

### Section style

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

Nothing else to configure — the layout is automatic.

💡 **Pro tip:** the featured image displays wide at the top of the post, so upload it at 1600 px+ across. Inside the post body, images you insert through the post editor render at the reading width — consistent widths keep the page feeling designed rather than pasted.


---

# 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-article.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.