# Regions

Regions allow you to adapt your brand messaging for different markets and languages. Each Region can have specific descriptions and writing rules that ensure your content is appropriately localized.

## Region Attributes

For each Region, you can define:

### Name

The region or market name (e.g., "United States," "France," "APAC," "Latin America").

### Description

Describe this region and who you are writing for, including their main characteristics. Consider:

* Language preferences
* Cultural nuances
* Market-specific terminology
* Regional product availability or pricing
* Local compliance requirements

### Writing Rules

Region-specific writing rules that override global writing rules when the rules conflict. Use one rule per line. You can toggle "Show global rules" to see how your region rules fit within your global guidelines.

{% hint style="info" %}
**Rule Override Behavior**: Region writing rules take precedence over global writing rules when they conflict. For example, if your global rule says "Use American English spelling" but your UK region rule says "Use British English spelling," the region rule will apply when the UK region is selected.
{% endhint %}

## Example

A company might define regions for:

**United States**

* Description: "English-speaking audience in the United States. Primary market with full product availability. References to pricing should use USD."
* Writing Rules:
  * Use American English spelling (color, organize, center)
  * Reference USD pricing
  * Use US date format (MM/DD/YYYY)

**France**

* Description: "French-speaking audience in France. Content should be culturally appropriate for the French market with local business context."
* Writing Rules:
  * All output must be in French
  * Use formal "vous" form for professional content
  * Reference EUR pricing
  * Use European date format (DD/MM/YYYY)

**United Kingdom**

* Description: "English-speaking audience in the UK. Content should reflect British English conventions and UK-specific context."
* Writing Rules:
  * Use British English spelling (colour, organise, centre)
  * Reference GBP pricing
  * Use UK date format (DD/MM/YYYY)

**APAC**

* Description: "Diverse audience across Asia-Pacific markets. Content should be culturally sensitive and avoid Western-centric assumptions."
* Writing Rules:
  * Avoid idioms that may not translate well
  * Be mindful of cultural references
  * Consider time zone differences in any scheduling references

## Adding Regions

1. Navigate to the **Regions** tab in your Brand Kit
2. Click **Add Region**
3. Enter the region name
4. Add a **Region Description** explaining who you are writing for in this region and their main characteristics
5. Add **Writing Rules** specific to this region (these will override global writing rules when they conflict)
6. Save your changes

## Region Variables

When a Region is selected, use these variables:

| Attribute                | Variable                             | Usage                                                                                  |
| ------------------------ | ------------------------------------ | -------------------------------------------------------------------------------------- |
| **Region**               | `{{brand_kit.region}}`               | Access the selected region's details.                                                  |
| **Region Name**          | `{{brand_kit.region.name}}`          | Name of the selected region.                                                           |
| **Region Description**   | `{{brand_kit.region.description}}`   | Understand region-specific context.                                                    |
| **Region Writing Rules** | `{{brand_kit.region.writing_rules}}` | Apply region-specific writing rules. These override global rules when conflicts occur. |


---

# Agent Instructions: 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:

```
GET https://docs.airops.com/context/brand-kit/regions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.