> For the complete documentation index, see [llms.txt](https://resources.viewrail.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.viewrail.com/install/forms/custom-gate-measurement-form.md).
# Custom Gate Measurement Form
Thank you again for choosing Viewrail. To help us create your new custom gate, please provide accurate details as requested on this form. Once completed, snap a photo or scan this form, and email it to your Viewrail Team Member.
***
### 1. Measurement Options (Please Choose One)
{% columns %}
{% column %} :circle: **Option 1 - Desired Gate Width**
We build to your exact requested width; you'll set posts as needed
{% endcolumn %}
{% column %} :circle: **Option 2 - Post-to-Post Opening**
We'll size the gate to fit between your existing posts or supports.
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %} :circle: **Option 3 - Top of Stairs (Against Structure)**
For gates at the top of stairs placed against a wall or structure
{% endcolumn %}
{% column %} :circle: **Option 4 - Top of Stairs (Between Railings)**
For gates at the top of stairs fitting between two railings or posts.
{% endcolumn %}
{% endcolumns %}
***
### 2. Handrail Height and Style Selection
{% columns %}
{% column %}
**Handrail Height (Check One)**
:circle: **36"** :circle: **39"** :circle: **42"**
{% endcolumn %}
{% column %}
**Gate Top (Check One)**
:circle: **Dome** :circle: **Domeless**
{% endcolumn %}
{% endcolumns %}
### Additional Notes or Comments
Use this space for any other details you want to include.
***
***
***
***
***
***
***
***
***
---
# 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://resources.viewrail.com/install/forms/custom-gate-measurement-form.md?ask=&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.
