> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/odoo-confluence-connector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/odoo-confluence-connector/user-guide/use-cases/current-use-cases/creating-a-gateway-between-confluence-pages-and-product-details.md).

# Creating a gateway between Confluence Pages and Product details

### **Creating a gateway between Confluence Pages and Product details**

Store all the technical documentation, user manuals, licensing information and any other documents of your products in Confluence, while keeping the product details in Odoo.

Let's create an Index Page in Confluence where you can access all your documentation and your products in a single Page.

{% hint style="success" %}
You can do the same for the products you develop and the products you use for internal purposes. You might want to store different information of these two, so let's see 2 examples for this use case.
{% endhint %}

### How to do it <a href="#creatingagatewaybetweenconfluencepagesandproductdetails-howtodoit" id="creatingagatewaybetweenconfluencepagesandproductdetails-howtodoit"></a>

1. Create the Index Page as the Parent Page of all your upcoming documentation
2. Add a **Page Properties Report Macro** to the Page. That will gather all the details you specify about a product in each page - and a direct link to it's documentation in Confluence
3. Setup the Page Properties Macro so it will find all the relevant Pages
   1. specify a label that you will add to each Product Documentation Page (e.g. own-products and internal-use-products)
   2. you can keep the Current Space setting as your documents will be added here as Child Pages
4. Save the Page
5. Create a Documentation Child Page for each Product&#x20;
6. Add a **Page Properties Macro** to the page (you can copy the macro from the first page after it's created
7. Make the Page Properties Macro hidden if you feel like not showing this info in the Pages (only in the Index Page)
8. *Inside the Page Properties Macro,* add a table
9. With the **Odoo Connect Macro**, add Odoo product details the you would like to show in the Index Page (e.g. Product name, Product Category, Product Owner, Technical Contact)
10. Add all the documentation to the Page as usual
11. Save the Page
12. Add the your chosen label to the current Page&#x20;
13. Check out the Index Page.

**Editing Own Product Documentation Page**

![](/files/EjGhuVKrtM58CXLrJo61)

**Editing Internal Product Documentation Page**

<br>

![](/files/Ah5SRLQ0RP08hSNLi7jh)

<br>

#### What does it look like? <a href="#creatingagatewaybetweenconfluencepagesandproductdetails-whatdoesitlooklike" id="creatingagatewaybetweenconfluencepagesandproductdetails-whatdoesitlooklike"></a>

If you made the Page Properties Macro hidden, you will not see any Odoo details in the Documentation Pages.

On the other hand, your Index Page will show a table of all your Child Pages and all the Product details for each Product as direct Links to Odoo.\
\
**Product Documentation Page with hidden Page Properties Macro**\
\
![](https://confluence.intra.meta-inf.hu/download/attachments/69897323/image2018-11-10_8-2-48.png?version=1\&modificationDate=1541833368239\&api=v2)

**Own Product Index Page**&#x20;

![](/files/JWyjQrI6B18mvYLr4Q7U)

**Internal Product Index Page**<br>

![](/files/qMwRIG58IPmOsCu1NSSd)

<br>


---

# 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.meta-inf.hu/odoo-confluence-connector/user-guide/use-cases/current-use-cases/creating-a-gateway-between-confluence-pages-and-product-details.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.
