> 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/pages/blog-page.md).

# Blog page

Your blog's index — a featured post at the top, then a grid of the rest, with tag filters.

## Content

| Setting         | What it does                            |
| --------------- | --------------------------------------- |
| Subheading      | An optional line under the blog title.  |
| Show tag filter | Links to the blog filtered by each tag. |

**The tag filter is hidden when no post is tagged**, so it never appears empty. Tags are added per post in **Content → Blog posts**. Tag consistently — "Materials" and "materials" would become two separate filters.

## Featured post

| Setting                | What it does                                       |
| ---------------------- | -------------------------------------------------- |
| Feature the first post | Leads each page with a wide panel.                 |
| Label                  | Shown above the panel.                             |
| Image position         | Left or Right.                                     |
| Color scheme           | Which scheme the panel uses. Defaults to scheme 4. |

Every page leads with the panel — the first post of that page, with the rest as cards beneath. So page two features its own first post, not the same one again.

## Layout

| Setting            | What it does       |
| ------------------ | ------------------ |
| Articles per page  | 3 to 24.           |
| Columns on desktop | 2 to 4.            |
| Columns on mobile  | One column or two. |

## Card

| Setting               | What it does                             |
| --------------------- | ---------------------------------------- |
| Aspect ratio          | Natural, Square, Portrait or Landscape.  |
| Show excerpt          | Every post, featured post only, or none. |
| Excerpt lines         | 2 to 6.                                  |
| Show tag on the image | The post's first tag, over its image.    |
| Read more label       | The words under each post.               |
| Show date             | When it was published.                   |
| Show author           | Who wrote it.                            |
| Show comment count    | How many comments it has.                |

**On excerpts:** *Featured post only* is a good middle — the lead post gets a proper introduction, and the cards below stay compact.

**On excerpt lines:** every card shows the same number, so a row ends level however long the titles are.

## Spacing and style

| Setting        | What it does                |
| -------------- | --------------------------- |
| Top spacing    | 0px to 120px.               |
| Bottom spacing | 0px to 120px.               |
| Color scheme   | Which scheme the page uses. |

## More than one blog

If you have several blogs, each gets this page automatically. To lay one out differently, create a template for it in the theme editor under **Blogs → Create template**, then assign it to that blog in your Shopify admin.


---

# 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/pages/blog-page.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.