> 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.

For the shortest overview of the whole ladder — browse, collect, plan, capture, share — see the [Docs home](/getting-started/readme.md).

## 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 and panel variants
* related public racks and public 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. See [Account and Privacy](/core-workflows/account-and-privacy.md) for sign-in options.

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 under [User Area](/core-workflows/user-area.md)

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 blank panels for spacing
* undo an edit that did not land well
* run rack analysis — power, function, layout, and signal — before committing to a layout

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 copies of the same module stay distinct as numbered instances, which matters when a patch uses more than one copy of the same hardware.

Patches also expose a graph view, a fullscreen mode, and a PNG export when you want to share the layout as an image.

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

### 6. Review sharing before you share links

Patcher supports both private workspace use and public sharing.

New racks and patches start Public. You can switch them to **Private** before creation or at any time later. See [Racks](/core-workflows/racks.md) and [Patches](/core-workflows/patches.md) for the Private toggle in detail, and [Account and Privacy](/core-workflows/account-and-privacy.md) for the full model.

For public discovery, both the item and the profile need to be public. See [Public Profiles](/core-workflows/public-profiles.md).

## Where to go next

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