> For the complete documentation index, see [llms.txt](https://www.projectpanoptes.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.projectpanoptes.org/build/getting-started/building-overview.md).

# Building Overview

A high-level overview of the build process.

## What Does it Take to Build a Robotic Telescope? <a href="#what-does-it-take-to-build-a-robotic-telescope" id="what-does-it-take-to-build-a-robotic-telescope"></a>

The PANOPTES telescope is designed so that all of the parts can be built with relatively inexpensive tools (e.g. a handheld electric drill, a soldering iron and a multimeter), many of which you may already own or have available to you. There is no need for a machine shop, though some operations are easier if you have access to a drill press. Anyone able to safely operate these tools (or learn to do so) should find the process of building the custom components and assembling the telescope to be accessible to them.

{% hint style="info" %}
If you are unsure of how to perform a fabrication step, we encourage you to find a local mentor with greater expertise (e.g. for soldering, you might look for an electrician, electrical engineer, robotics or amateur radio hobbyist).
{% endhint %}

You may also find online tutorials helpful; we provide links in [this document](/build/getting-started/safety-guide.md) to some tutorials that you may find useful. And please don’t hesitate to post questions on the [PANOPTES Forum](https://forum.projectpanoptes.org/).


---

# 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://www.projectpanoptes.org/build/getting-started/building-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.