> For the complete documentation index, see [llms.txt](https://pwa.spomky-labs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pwa.spomky-labs.com/1.2.x/the-manifest/application-information/direction-and-language.md).

# Direction and Language

The PWA dir and lang parameters.

Progressive Web Apps (PWAs) can be tailored for different languages and writing directions through the use of the `dir` and `lang` parameters in the HTML tag.

By properly setting the `dir` and `lang` parameters, you ensure better user experience, accessibility, and potentially improved SEO for your PWA.

Please note that those values should be in accordance with the ones set as `<html>` tag attributes.

```html
<html dir="ltr" lang="en">
</html>
```

### The `dir` Parameter

The `dir` parameter specifies the text directionality of the content in your PWA. It can have one of three values:

* `ltr`: Left-to-right, which is used for languages that are read from the left to the right (like English).
* `rtl`: Right-to-left, for languages read from the right to the left (like Arabic or Hebrew).
* `auto`: Automatically determines the direction based on the content.

Example usage in HTML:

### The `lang` Parameter

The `lang` parameter declares the default language of the text in the page. This is important for accessibility tools and search engines.

### Configuration

{% code title="/config/packages/pwa.yaml" lineNumbers="true" %}

```yaml
pwa:
    manifest:
        enabled: true
        dir: "ltr"
        lang: "en"
```

{% endcode %}


---

# 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://pwa.spomky-labs.com/1.2.x/the-manifest/application-information/direction-and-language.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.