> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/post-and-beam-framing.md).

# Post & Beam Framing

{% hint style="danger" %}
As of **February 2025**, this product has been officially **discontinued** and removed from our portfolio therefore it is **no longer in development**, and no new functionality will be added.

This help page remains available to assist existing users with the current functionality.
{% endhint %}

### Sample Projects

Try out the Post & Beam Framing software in one of your projects or in our Sample Projects.

{% tabs %}
{% tab title="Metric Sample Projects" %}
{% file src="/files/GfNgEDcNDQ5iOAKTzleP" %}
{% endtab %}

{% tab title="Imperial Sample Projects" %}
{% file src="/files/PVtmeYhPQMS9tiikHf8f" %}
{% endtab %}
{% endtabs %}

### Recent Webinar Recording

{% embed url="<https://youtu.be/9JwtEnJdV9U?si=WSi2OTBxeI19-dIz>" %}

### Support and Inquiries

For technical questions regarding the software, please [**submit a support ticket**](https://emea.support.arkance.world/hc/en-gb/requests/new) or write to <support@besmart.software>.

For pricing and licensing inquiries, kindly contact us at <info@besmart.software>.

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


---

# 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.besmart.software/3d-modeling-and-design/post-and-beam-framing.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.