> For the complete documentation index, see [llms.txt](https://seyarat.gitbook.io/seyarat-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seyarat.gitbook.io/seyarat-docs/configuration/top-bar-builder.md).
# Top Bar Builder
The Top Bar is the narrow area above the main Header. It is suitable for a short announcement, phone number, business hours, location, or social links.
{% hint style="info" %}
Keep the Top Bar short. Too much content makes the Header tall, especially on mobile.
{% endhint %}
#### Create and design
1. Open **N3Theme** → **Top Bar** and click **Add New**.
2. Enter a clear **title**, then click **Publish** and **Edit with Elementor**.
3. Add one compact row with useful text, links, or social icons.
4. Check **Desktop**, **Tablet**, and **Mobile**; wrap or hide non-essential items.
5. Click **Update**.
#### Assign globally
1. Open **N3Theme** → **Theme Options → Builder Option → Top Bar**.
2. Select the template in **Top Bar Type**.
3. To use the built-in version, select **Default**.
4. For Default, enter the content in Text.
5. Click **Save Changes.**
#### Override and test
1. Edit the page and open **Page Options** → **Top Bar Option**.
2. Choose **Default**, a **Top Bar** template, or **None**.
3. Click **Update**.
4. Test while logged out and on mobile.
5. If stale, clear Elementor, site, server, and browser caches.
---
# 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://seyarat.gitbook.io/seyarat-docs/configuration/top-bar-builder.md?ask=&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.
