> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/getting-started/quick-start.md).

# Quick start

This is the fastest way to get practical value out of Patcher.

## The short version

1. Browse modules without signing in.
2. Create an account when you want to save your own work.
3. Add the modules you own to your collection.
4. Build a rack to check fit and layout.
5. Create a patch to save routing and notes.
6. Review your sharing settings before you share links publicly.

## First useful session

### 1. Browse the module database

Go to **Modules** and search for the hardware you already own, want to buy, or want to compare.

Open module detail pages to check:

* size and format
* power information
* panel images
* related public racks and patches
* manual links when they are available

Read more: [Modules](/core-workflows/modules.md)

### 2. Create an account

You can explore public data without an account, but you need one to build your own workspace.

After signing up, your workspace becomes available through **User Area**.

### 3. Add your real modules to your collection

Your collection is the source list for the rest of the app.

Once modules are in your collection, they become available for:

* planning racks
* building patches
* gathering manuals in one place

Read more: [Collection](/core-workflows/collection.md)

### 4. Build your first rack

Create a rack when you want to test fit, compare layouts, or document an existing case.

You can:

* add modules from your collection
* move modules visually
* duplicate modules
* replace modules with blanks for spacing
* review fit plus rack analysis tools such as power and function views

Read more: [Racks](/core-workflows/racks.md)

### 5. Capture your first patch

Create a patch when you want a reusable memory of a session, not just a temporary note.

Use patches to save:

* the modules involved
* cable routing
* names and descriptions
* notes worth revisiting later

Repeated modules stay distinct, which matters when a patch includes more than one copy of the same hardware.

Read more: [Patches](/core-workflows/patches.md)

### 6. Review sharing settings before you share links

Patcher supports both private workspace use and public sharing.

Public browsing only shows racks and patches that are marked public and belong to a public profile.

New racks and patches currently start public, so check their sharing toggle if you want to keep them private while you work.

Read more:

* [Public Profiles](/core-workflows/public-profiles.md)
* [Account and Privacy](/core-workflows/account-and-privacy.md)

## Where to go next

* [User Area](/core-workflows/user-area.md)
* [FAQ](/project/the-project.md)
* [Contact / Community](/project/contact-us-help-community.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patcher.xyz/getting-started/quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.