> For the complete documentation index, see [llms.txt](https://docs.lufavo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lufavo.com/roomfolk/blocks/article-blocks.md).

# Blog post blocks

The blog post page is built from blocks, so you control what each post shows and in what order. Edit them in the theme editor with a blog post open.

## Heading

The post title. No settings.

This is the page's Heading 1, so keep it on the page.

## Featured image

| Setting      | What it does                        |
| ------------ | ----------------------------------- |
| Aspect ratio | Natural, Landscape, Wide or Square. |

**Natural** keeps each image's own proportions. The fixed shapes crop every post image the same way, which keeps a blog looking consistent when the images come from different places.

Only shows for posts that have a featured image set.

## Date and author

| Setting     | What it does                     |
| ----------- | -------------------------------- |
| Show date   | The date the post was published. |
| Show author | Who wrote it.                    |

## Excerpt

The post's excerpt, shown under the title. No settings.

Excerpts are written per post in your Shopify admin, under **Content → Blog posts**. Where a post has no excerpt, this block shows nothing.

## Tags

The post's tags. No settings.

Tags are added per post in your Shopify admin. They double as the filters on the [blog page](/roomfolk/pages/blog-page.md), so tag consistently — "Materials" and "materials" would become two separate filters.

## Content

The body of the post. No settings.

Formatting you apply in Shopify's post editor — headings, lists, quotes, links, images — is styled by the theme to match the rest of the store.

## Comments

Comments are not a block; they appear automatically when you turn them on for a blog in your Shopify admin, under **Content → Blogs → Manage blog**.

When they are on, the post shows the existing comments and a form for leaving one. If you have set comments to be approved before they appear, someone leaving one is told their comment is awaiting approval rather than being left wondering where it went.


---

# 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.lufavo.com/roomfolk/blocks/article-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.