> 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/how-to/feature-pattern-truss/edit-tools-for-feature-pattern-trusses/stub-truss.md).

# Stub Truss

Before you begin, select a `Feature Pattern` truss.

## Step 1 - Click `Edit Truss` and choose `Stub Truss`

{% hint style="info" %}
Note

This option is only available for Feature Pattern trusses
{% endhint %}

## Step 2 - Choose how you would like to stub the truss, such as `Right Side` and `4'` in `Stub Distance`

You can choose to stub the truss on the left or right side. You can also select whether you would like to input the distance to the stub or how much of the span should remain after the stub.

## Step 3 - Click `Stub` to apply your changes

<figure><img src="https://2598702589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIkcl8vW0QKiqUIx7Xdc%2Fuploads%2FHtTe5ytbvYllSK7oeIRO%2FEditTrussTools_StubTruss.gif?alt=media&amp;token=75b8523f-5fb1-43bd-b11f-55c87ad5fdac" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Warning

This feature may not work for feature pattern trusses that are gabled or that have been webbed manually. In these cases, you will see Error: "Unable to Stub"
{% endhint %}


---

# 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/how-to/feature-pattern-truss/edit-tools-for-feature-pattern-trusses/stub-truss.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.