> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/shop-accessories/super-pit/assembly-instructions/superstation.md).
# SuperStation
The following sections will have all necessary information for the assembly of the SuperStation.
## Step 1
Install the Main Rails onto the Driver Station Base using a total of ten #10-32 x 3/8"L bolts and secure them using #10-32 nuts.
## Step 2
Attach the Laptop Plate to the Main Rails in your desired location using four #10-32 x 3/8"L bolts and nuts.
## Step 3
Install the Side Rails and Corner Gussets using #10-32 x 3/8"L bolts in the locations shown below.
{% hint style="info" %}
Ensure that the bottom bolts go through both the Base plate and the Side Rail.
{% endhint %}
## Step 4
Install the Port Covers in the appropriate locations using four #10-32 x 3/8"L bolts and #10-32 nuts.
{% hint style="info" %}
This step can be skipped if the Port Covers are not being used.
{% endhint %}
## Step 5
Install the handles using the included 1/4"-20 x 1"L bolts.
{% hint style="info" %}
The included Tube Nuts need to be pressed into the Handles before the installation process.
{% 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.wcproducts.com/welcome/shop-accessories/super-pit/assembly-instructions/superstation.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.
