> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/design/explanation/trusslink.md).

# TrussLink

When you download or share any truss design drawing generated from Paragon, the file is embedded with smart links. We call this Paragon TrussLink.

Thanks to Paragon's modern cloud infrastructure, all changes made to projects and designs update automatically regardless of the device or location. You can reference the section on [Shared Component sets](https://docs.paragontruss.com/design/explanation/shared-component-sets.md) in order to create a shareable file or link. This link will allow anyone to view your truss designs from anywhere, even if they don't have a Paragon account.

The QR code will be included in the TDDs. Additionally, clicking on a component in the TDD will open a link in your browser to load that component in Paragon Design. Clicking on a specific plate for example will load the truss design and zoom in automatically to the plate you have selected.

Download the sample below to test it yourself.

{% file src="/files/JhmsCEcdMhD58RLj9cZ7" %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.paragontruss.com/design/explanation/trusslink.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
