> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/broadcast-v5/siblings/product-siblings/siblings-color.md).

# Siblings color

Metafield editor

> Feature introduced in Broadcast 3.5

The first required metafield is **`theme.sibling_color`** 

```
theme.sibling_color
```

For the content type, select 'Single line text' and choose the 'One value' option.

The metafield is also used for the swatch label. This will help with identifying the color version of the current product:

<figure><img src="https://content.gitbook.com/content/j8jzXN4KKXAfQhgbN5lO/blobs/UxkNpfujn3qworaUBvRS/Screen%20Shot%202022-10-06%20at%203.04.24%20PM.png" alt=""><figcaption></figcaption></figure>

Start by defining a Product metafield. You can name it 'Sibling Color' so that you can more easily find it later.

{% hint style="info" %}
Important step: Change the Namespace from **custom** to **theme**.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/j8jzXN4KKXAfQhgbN5lO/blobs/X2eidUgvzvRxgNZpCBYX/siblings%20color2.gif" alt=""><figcaption></figcaption></figure>

Adding a description is optional but be sure to select the correct content type. Choose 'Single line tex&#x74;**'** and set it to 'One valu&#x65;**'**:

<figure><img src="https://content.gitbook.com/content/j8jzXN4KKXAfQhgbN5lO/blobs/z56s5EzjwDcZwkyCXqt9/siblings%20color4.gif" alt=""><figcaption></figcaption></figure>

**Save** the definition.

### Check the saved metafield

Your final metafield should look like this:

<figure><img src="https://content.gitbook.com/content/j8jzXN4KKXAfQhgbN5lO/blobs/rU40yyL350I3gw3Z3UNn/Screen%20Shot%202022-10-06%20at%203.28.15%20PM.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please ensure you change the Namespace and key to this custom version for Broadcast:\
\
**`theme.siblings_color`**\
\
By default, the namespace begins with '**custom'**. This namespace will not be recognized by Broadcast. You have to change it to '**theme**'.

This is a good distinction to make and it helps keep your store, custom, theme, and app metafields separate.
{% endhint %}

### Next step

We require a second metafield to be defined:

{% content-ref url="/pages/OqnhhJ6fbBrXGmw50xzc" %}
[Siblings collection](/broadcast-v5/siblings/product-siblings/siblings-collection.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://broadcast.presidiocreative.com/broadcast-v5/siblings/product-siblings/siblings-color.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.