# Configuration

### Base Href Tag

The base href tag tells the plugin where it is located, and must match the path where it is served from. If your web server hosts the plugin at `https://my-server.com/my-talque-plugin` then the base href tag must be:

<pre class="language-html"><code class="lang-html">&#x3C;base href="/<a data-footnote-ref href="#user-content-fn-1">my-talque-plugin</a>/">
</code></pre>

To verify that the setting is correct, try opening the plugin and then reloading the browser. If the base href is correct then the plugin should reload at the same place.

### Content IDs

There are two identifier that determine the content that is visible. First, the org id is the unique id of your network. The other id is the plugin configuration; In simple cases you have one plugin per network, so there is a unique config id. But in more complicated installations you could have the same network shown in two different plugins. These IDs are set as data attributes on the plugin root tag, where our plugin bootstraps:

```html
<rli-tq-plugin-root
    data-org-id="DRl8NY32VVvIa2s0FYTx" 
    data-config-id="UABcnEgqzljwZf5qiGb3" 
    data-backend="https://www.talque.com">
</rli-tq-plugin-root>
```

### Custom Menu / Header

Our template `index.html` file has a dummy header that you can replace with your own header, or a custom menu to link to other pages on your website:

```html
<!-- replace this with your own header -->
<div class="border-box h-20 tw-flex tw-flex-none justify-center items-center justify-between px-24">
    ...
</div>
<!-- end replace -->
```

[^1]:


---

# 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://talque.gitbook.io/public/talque-plugin/configuration.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.