> For the complete documentation index, see [llms.txt](https://help.orbe.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orbe.app/developer-reference/snippets/language-order-customization.md).

# Language Order Customization

In Orbe, the language list within the selector is ordered by default according to how it's being added to Shopify. However, it's possible to customize this order using CSS, allowing you to prioritize certain languages by placing them at the top of the list.

For example, in this language selector, you can see that Dansk and Italian are at the top when you open the selector:

Here's a step-by-step guide on how to achieve this through Custom CSS:

<figure><img src="https://1070558711-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9pRSk2pXNrLaA6YXOW5G%2Fuploads%2FKROZSy1pcVpEe91RongZ%2FLanguage%20Order.gif?alt=media&amp;token=218f94a5-c490-450d-9633-c903bb54eb95" alt=""><figcaption></figcaption></figure>

**Step 1: Modify the display of the list**

To start, we need to change the display setting of the language list to a grid layout. This allows us to reorder the languages:

```css
.md-form__select__language__list {
    display: grid;
}

.md-form__select__language__list[hidden] {
    display: none;
}
```

**Step 2: Set Default Order**

Next, set a default order for all languages in the list. This ensures that any language not explicitly reordered will follow this default setting:

```css
.md-form__select__language__list li {
    order: 2;
}
```

**Step 3: Reorder Specific Languages**

Now, you can select specific languages and assign them a different order. In this example, we're moving English (EN) and Spanish (ES) to the top of the list:

```css
.md-form__select__language__list li[data-locale="it"], 
.md-form__select__language__list li[data-locale="da"] {
    order: 1;
}
```

Adding these CSS classes allows you to customize the order of languages within the Orbe selector easily. Just replace `"it"` and `"da"` with the language codes of your preferred languages to tailor the list to your needs. This refers to the ISO two-letter code (alpha-2) of the language.

## Complete Code Example

Here's the complete CSS snippet for repositioning Italian and Dansk at the top of the list:

```css
.md-form__select__language__list {
    display: grid;
}

.md-form__select__language__list[hidden] {
    display: none;
}

.md-form__select__language__list li {
    order: 2;
}

.md-form__select__language__list li[data-locale="it"], 
.md-form__select__language__list li[data-locale="da"] {
    order: 1;
}
```

With this customization, you can enhance the user experience by highlighting the most relevant languages for your customers.


---

# 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://help.orbe.app/developer-reference/snippets/language-order-customization.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.