> For the complete documentation index, see [llms.txt](https://wplake.gitbook.io/advanced-views/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wplake.gitbook.io/advanced-views/display-content/mount-points.md).

# Mount Points

### How to use it

[Add a new Layout](/advanced-views/getting-started/introduction/creating-your-first-layout.md) and assign fields as usual.

Switch to the **Mount Points** tab.

**Click** on the **Add Mount Point** button.

In the **Specific posts** field select which posts to limit the mount point to.

Or instead use the **Post Types** field to limit the mount point to all posts of the same type.

Determine where you want to show your *Layout*, then **add** the **Unique word**, **string** or **HTML** piece to ‘Mount’ to using the **Mount Point**. If left empty the content will be used as a mount point.

In the [Shortcode Arguments](/advanced-views/shortcode-attributes/common-arguments.md) field add available arguments to your shortcode to [restrict visibility](/advanced-views/shortcode-attributes/common-arguments.md) or to [define another object id](/advanced-views/shortcode-attributes/layout-shortcode.md#from-another-source).

{% hint style="warning" %}
Note: this feature uses 'the\_content' theme hook, so mount points won't work if your theme or a specific template doesn't call it or calls it outside of the standard loop. 
{% endhint %}

### Custom theme template

If you’re going to create your own theme template, see below for a sample on the correct standard loop, you will have to use this as a basis in order for the Mount Points feature to work with pages that use your custom template files.

<pre class="language-php" data-overflow="wrap"><code class="lang-php"><strong>&#x3C;?php
</strong><strong>// even if your template is designed for a single page/CPT item
</strong><strong>// you must use the loop, it's the default WordPress way 
</strong><strong>// (see default themes, like twentytwenty) 
</strong><strong>while ( have_posts() ) {
</strong><strong>    // it's a part of the loop, this call 'loads' data about the current post/CPT item
</strong>    the_post();
    
    // content can be printed either using the 'the_content()' function
    the_content();
    
    // or can be get using the 'get_the_content()' function, 
    // but only along with the "apply_filters( 'the_content', $content )" call
    $content = get_the_content();
    $content = apply_filters( 'the_content', $content );
    
    // todo print post fields here
}
</code></pre>


---

# 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://wplake.gitbook.io/advanced-views/display-content/mount-points.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.