# Header Menu

Access your blog **Layout** > and click on the **Edit Icon** > in the **Header Menu** gadget.

### Default Links and Sub Links

Default Link Example: `Features`&#x20;

SubLink Level 1 Example: `_Level 1` “Before the Title add 1 underscore”&#x20;

SubLink Level 2 Example: `__Level 2` “Before the Title add 2 underscore”

**Example:**

<figure><img src="/files/pqXr9qk0ZbFHNANMmcaH" alt="Submenu" width="459"><figcaption></figcaption></figure>

{% hint style="info" %}
INFO: Level 2 Links must be between or below level 1 links.&#x20;
{% endhint %}

### Mega Menu&#x20;

Shortcode: `{getPosts} $label={Your Label} $type={Your Label} $color={Hex Color}`&#x20;

Label Options: `Label Name` or `recent`

Type Options: `mega`, `tabs`

Color Attribute: This attribute is optional and must be entered only if you want to add a custom color.&#x20;

Hex Colors: <https://flatuicolors.com/>

#### What are Label Name?

<figure><img src="/files/y9oIOeor9Lp5KB2dkzom" alt="Label name" width="525"><figcaption></figcaption></figure>

**Mega Example:**&#x20;

In this type the attribute `$type={}` is not required.

<figure><img src="/files/elOsWVzAxt96OgRpvOga" alt="Mega menu" width="428"><figcaption></figcaption></figure>

**Tabs Example:**&#x20;

In this type you can add as many labels as you like and separate them by `/`. The `$type={}` attribute is required.

<figure><img src="/files/8oq6hkQ2Rq41bMW1WVEG" alt="Mega tabs" width="475"><figcaption></figcaption></figure>

{% hint style="success" %}
SAVE: After adding all the desired links and organizing them in the correct position, click on the Save Button.
{% endhint %}


---

# 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.probloggertemplates.com/guides/magspot/getting-started/header-menu.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.
