> 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/core-workflows/search-and-discovery.md).

# Search and Discovery

Patcher is built to help you find things quickly across both the public library and your own workspace.

## Public discovery

Discovery usually starts with **Modules**, then expands into related public racks and patches.

This is useful when you want to:

* compare modules before buying
* see how other people are using a module
* move from a single piece of gear into usable context

## Workspace search

Inside **User Area**, one search query filters your modules, racks, patches, manuals, and comments at the same time.

That matters once your workspace holds enough material that scrolling stops being efficient.

This is not a single combined cross-entity search result page. Each section keeps its own results while reusing the same query.

User Area itself requires a signed-in account.

## Discovery surfaces that matter

Patcher currently supports discovery through:

* module search and browsing, with grouped Any / All tag filters and manufacturer filters
* related public racks and patches surfaced from module detail pages
* public rack browsing
* public patch browsing
* public profiles
* global search inside your [User Area](/core-workflows/user-area.md)

## Community trends

**Community trends** is the public read-out of what is currently drawing attention across Patcher — which modules are being added, which racks are being viewed, which patches are being opened. Use it when you want a discovery entry point that is not driven by a specific search or a module you already know about.

Community trends is a public surface, so it works whether you are signed in or not. Treat it as a starting point for exploration rather than a ranking of quality.

## Best way to use it

1. Start broad in the public catalogue or in community trends.
2. Save the modules that matter to your collection.
3. Use User Area search once your own workspace grows.
4. Follow related public examples when you need context, ideas, or comparisons.

## Related pages

* [Modules](/core-workflows/modules.md)
* [User Area](/core-workflows/user-area.md)
* [Racks](/core-workflows/racks.md)
* [Patches](/core-workflows/patches.md)
* [Public Profiles](/core-workflows/public-profiles.md)
* [Modular Glossary](/reference/modular-glossary.md)