> 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/general-blocks.md).

# General blocks

Blocks are the pieces that go inside a section. These ten are available in most sections — the hero, image banner, rich text, custom section, the footer and others.

Add them with **Add block** inside a section, and drag them to reorder.

## Heading

| Setting              | What it does                                    |
| -------------------- | ----------------------------------------------- |
| Heading              | The heading text.                               |
| Gradient accent line | An extra line beneath it, in your accent color. |
| Heading level        | Heading 1, 2 or 3.                              |
| Heading size         | Small, Medium or Large.                         |
| Alignment            | Left, centered or right.                        |

**Level and size are different things.** The level decides where the heading sits in the page's outline, which matters for search engines and screen readers. The size decides how big it looks. You can have a large-looking Heading 3.

**Use one Heading 1 per page and do not skip levels.** Most pages already have their Heading 1 — the product name, the collection title, the hero headline — so blocks you add are usually Heading 2 or 3.

## Text

| Setting    | What it does                      |
| ---------- | --------------------------------- |
| Text       | The text.                         |
| Text style | Heading, Subheading or Body text. |
| Alignment  | Left, centered or right.          |

## Kicker

| Setting | What it does                              |
| ------- | ----------------------------------------- |
| Text    | The small line that sits above a heading. |

Kickers are drawn with the accent icon set in [Typography](/roomfolk/theme-settings/typography.md).

## Button

| Setting      | What it does                  |
| ------------ | ----------------------------- |
| Button label | The text on the button.       |
| Link         | Where it goes.                |
| Button style | Accent, Primary or Secondary. |
| Alignment    | Left, centered or right.      |

Use one strong button per section. If you need two, make the second one Secondary so it is clear which is the main action.

## Image

| Setting             | What it does                                        |
| ------------------- | --------------------------------------------------- |
| Image               | The image.                                          |
| Link                | Optional. Makes the image clickable.                |
| Aspect ratio        | Natural, Square, Portrait, Landscape or Wide.       |
| Use rounded corners | Rounds the corners to match the theme's card shape. |

**Natural** keeps the image's own proportions. The others crop to a fixed shape, which is what you want when several images need to line up.

## Badges

A row of up to three short promises, each with an icon.

| Setting | What it does                                                       |
| ------- | ------------------------------------------------------------------ |
| Badge   | The text.                                                          |
| Icon    | Delivery, Returns, Guarantee, Sustainable, Support, Spark or None. |

Leave a badge's text empty to hide it.

## Divider

| Setting   | What it does                                     |
| --------- | ------------------------------------------------ |
| Show line | Draws a line. Turn it off for invisible spacing. |
| Thickness | 1px to 8px.                                      |
| Spacing   | 0px to 100px above and below.                    |

With **Show line** off, this is just a spacer — useful for pushing two blocks apart without a visible rule.

## Group

Holds other blocks together so they can be arranged as a unit.

| Setting          | What it does                   |
| ---------------- | ------------------------------ |
| Layout direction | Horizontal or Vertical.        |
| Alignment        | Left, centered or right.       |
| Padding          | 0px to 200px inside the group. |

Use it to put two buttons side by side, or to indent a set of blocks together.

## Newsletter

| Setting   | What it does                                      |
| --------- | ------------------------------------------------- |
| Heading   | The heading above the field.                      |
| Body text | A line explaining what people are signing up for. |

Signups go to your Shopify customer list, marked as accepting marketing. For a full-width version, use the [Email signup](/roomfolk/sections/email-signup.md) section.

## Custom Liquid

| Setting     | What it does                        |
| ----------- | ----------------------------------- |
| Liquid code | Code to render inside this section. |

Same as the [Custom Liquid section](/roomfolk/sections/custom-liquid.md), but placed within another section. **Invalid Liquid will stop the page rendering** — read that page before using it.


---

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