# Documentation improvements

**URL:** <https://community.interop.io/t/documentation-improvements/327>\
**Category:** General\
**Tags:** Discussion, Feedback\
**Created:** [November 5, 2025, 1:26pm UTC](https://community.interop.io/t/documentation-improvements/327 "2025-11-05T13:26:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)\
**Post date:** [November 5, 2025, 1:26pm UTC](https://community.interop.io/t/documentation-improvements/327/1 "2025-11-05T13:26:56Z")

</div>

How can we improve the product docs at [docs.interop.io](https://docs.interop.io/)? Is there anything you wish was clearer, covered in more details or structured differently?

---

<div class="post-metadata">

**Author:** ![anil](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/anil/32/54_2.png) [@anil](https://community.interop.io/u/anil)\
**Post date:** [November 5, 2025, 1:47pm UTC](https://community.interop.io/t/documentation-improvements/327/2 "2025-11-05T13:47:46Z")

</div>

I would love to see documentation with actual examples. This will especially help with various extensibility settings for example

---

<div class="post-metadata">

**Author:** ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)\
**Post date:** [November 5, 2025, 4:29pm UTC](https://community.interop.io/t/documentation-improvements/327/3 "2025-11-05T16:29:59Z")

</div>

Hi Anil, thanks for the feedback, there’s definitely room for improvement here!  
Do you mean more ode snippets, more use cases or something like a whole tutorial with examples of this type - [io.Connect Desktop Documentation - JavaScript Tutorial](https://docs.interop.io/desktop/tutorials/javascript/index.html#1_initial_setup)  
Or are you thinking about some code examples in the API reference?

---

<div class="post-metadata">

**Author:** ![anil](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/anil/32/54_2.png) [@anil](https://community.interop.io/u/anil)\
**Post date:** [November 5, 2025, 5:30pm UTC](https://community.interop.io/t/documentation-improvements/327/4 "2025-11-05T17:30:30Z")

</div>

Hi  
In general the documentation is very good and covers each setting/api very thoroughly. The Tutorial is also very comprehensive. However I felt there were areas where we needed information and there was not a lot of detail

For example: When we integrated our system with Bloomberg, we used the following page in documentation and it did not provide us with a clear path on how to approach this issue. We wanted information on what to ask Bloomberg, what kind of license should we ask them for, how should we go about building a POC (a simple example would have helped here), etc

[https://docs.interop.io/adapters/bloomberg/overview/index.html](https://docs.interop.io/adapters/bloomberg/overview/index.html)

Thank you

Anil

---

<div class="post-metadata">

**Author:** ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)\
**Post date:** [November 5, 2025, 5:53pm UTC](https://community.interop.io/t/documentation-improvements/327/5 "2025-11-05T17:53:24Z")

</div>

That’s super helpful. Yes, some of the Adapters documentation and other addon-s can be extended with details. If there are other pages/sections where you have a question or feedback, please always post it here, so we can improve it.  
Thanks!

---

<div class="post-metadata">

**Author:** ![anil](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/anil/32/54_2.png) [@anil](https://community.interop.io/u/anil)\
**Post date:** [November 5, 2025, 6:09pm UTC](https://community.interop.io/t/documentation-improvements/327/6 "2025-11-05T18:09:51Z")

</div>

Ok sure, thank you. Your team has been super helpful when we reach out to them
