> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-nav/settings/how-can-i-create-collection-pages-using-inline-page-nav.md).

# How can I create Collection Pages using Inline Page Nav?

{% stepper %}
{% step %}

### Ensure that the URLs inputted into the "Link" field for categories and sub-categories in Maker Nav match precisely with the URLs currently used for those collections on our side. We will display Nav Collection Landing Pages/Product Listing Pages (CLPs/PLPs) only if there's an exact URL match. Additionally, it's vital to ensure that each URL is utilized only once within the Maker Nav.

<figure><img src="/files/986yCDuB7iKLqO8oOWD8" alt="How can I create Collection Pages using Inline Page Nav? — step 1"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Tip! "Pre-Publish" check, found under the Info tab, identifies duplicate links in the Nav that prevent CLPs from loading the correct category after switching to the Maker Collections template. By clicking on the menu items displayed on the screen below, you will be directed to the corresponding item in the Nav where you can correct the error.

<figure><img src="/files/2Un3HrzHfTjsBqFAmCXO" alt="How can I create Collection Pages using Inline Page Nav? — step 2"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Copy the embed code Inline

<figure><img src="/files/9ABWiVyDmc4d2BgB0GB1" alt="How can I create Collection Pages using Inline Page Nav? — step 3"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### The embed code contains two parts- The script tag + div. The script tag must be added to the head of the page and the div in the main container on the page.

The script would look like this :

The div would look like this:

\
\[\[\<script src="<https://showside.maker.co/smartnav-v2-inline.js>" async="">\</script>]]
{% endstep %}

{% step %}

### Since an Inline Nav will replace the current CLP or PLP, duplicate your CLP or PLP template in your CMS and replace all the body with the embed code copied for Inline, leaving only the site header and footer.

{% endstep %}

{% step %}

### Things to keep in mind while creating the template:

1- Set the template width to 100% 2- Remove any unnecessary Javascript/CSS elements not relevant to this template. 3- Prioritize loading the Nav's script to prevent potential page load issues. 4. Set the minimum height of this template to 1000px
{% endstep %}

{% step %}

### To enable the Inline Page feature, toggle ON "Enable inline page nav" under the general Global settings.

<figure><img src="/files/gBI14rmq9RJDsPbg5VVp" alt="How can I create Collection Pages using Inline Page Nav? — step 7"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Switch the current template used on the CLPs or PLPs to the new Maker template.

{% endstep %}

{% step %}

### Tip! We advise launching category pages individually and thoroughly reviewing the settings prior to each launch to minimize potential problems.

{% endstep %}

{% step %}

### In the event of a missing or mismatched URL in the link section for any collections within your sitewide nav, Maker will automatically default to displaying the sitewide Nav.

{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maker.co/maker-nav/settings/how-can-i-create-collection-pages-using-inline-page-nav.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.