> 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/header-footer-builder.md). # Header / Footer Builder Create Header and Footer by Elementor ### Create Header and Footer #### Create the template 1. Open **N3Theme** → **Header** or **N3Theme** → **Footer**. 2. Click **Add New**. 3. Enter a clear title. 4. Click **Publish**, then **Edit with Elementor**. *A published template opens in **Elementor**.* **Create Header**

**Create Footer**

#### Design with real content 1. For a **Header**, add the **logo** and **menu**. 2. Add only needed account, search, compare, cart, or action controls. 3. For a **Footer**, create clear link and information columns. 4. Add contact, social, and copyright details. 5. Replace placeholders with real content and working links. *The Header or Footer contains complete, usable content.*

#### Make it responsive 1. Check **Desktop**, **Tablet**, and **Mobile** in **Responsive Mode.** 2. Confirm the mobile menu opens and closes. 3. Stack **Footer** columns and reduce large gaps where needed. 4. Click **Update**, then **Preview**. *The layout remains readable and usable at all three sizes.*

#### Assign it globally 1. Open **N3Theme** → **Theme Options** → **Builder Option.** 2. Select the template in **Header Type** or **Footer Type**. 3. Briefly review sticky behavior and colors. 4. Click **Save Changes**. *Pages without overrides use the selected template.*

#### Override and test a page 1. Open **Pages** → **edit** → **Page** **Options**. 2. Choose **Default**, a template, or **None**; use overlay only if needed. 3. Click **Update**. 4. Test logged out and on mobile. 5. If changes look stale, clear Elementor, site, server, and browser caches. *The page uses its intended layout and works for visitors.*

--- # 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/header-footer-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.