> 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/installation-hub-overview.md).

# Installation Hub Overview

Start here to find installation guides, reference pages, and forms for each product family.

### How to use this hub

1. Open your product family.
2. Follow the installation guide in order.
3. Use the reference pages and forms when needed.

{% hint style="info" %}
If you are not sure where to begin, start with your product family first.
{% endhint %}

### Choose your product family

* [FLIGHT Mono](/install/flight-mono/steel-first-install.md)\
  Installation guidance for mono stair configurations.
* [FLIGHT Stack](/install/flight-stack/steel-frame-install.md)\
  Steel frame and tread installation guides.
* [FLIGHT Cantilever](/install/flight-cantilever/steel-first-install.md)\
  Installation guidance for cantilever stair systems.
* [FLIGHT Spiral](/install/flight-spiral/bolt-together-spiral-staircase-installation-guide.md)\
  Spiral staircase installation guides by system type.
* [Express Cable Railing](/install/express-cable-railing/level-surface-mount-post-install.md)\
  Post hardware, handrail, infill, and final touch steps.
* [Signature Cable Railing](/install/signature-cable-railing/post-order-of-installation.md)\
  Post installation, infill paths, and handrail guidance.
* [Glass Railing](/install/glass-railing/fascia-requirement-for-side-mount.md)\
  Base rail, standoff pin, infill, handrail, and finishing steps.


---

# 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/installation-hub-overview.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.