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

# Getting Started

Workshop allows you to **publish, advertise, and earn** from your items. It provides a broad set of features for both publishers and end users, making the storefront easy to use and reliable to manage.

## Core Concepts

Before publishing, it's important to understand the key concepts used in Workshop:

* **Storefront** - the main Workshop UI where users search, view, subscribe to, or purchase items;
* **Publishing Tool** - the area where item authors create, update, and manage their entries in the storefront;
* **Item** - a single Workshop entry. This can be a script, a library, or a config;
* **Build** - a specific version of an item that gets delivered to the end user;
* **Branch** - a channel that holds a single build (e.g. *stable*, *beta*);
* **Dependency** - a required library that an item relies on to function;
* **Capability** - a permission that unlocks restricted API functions (e.g. filesystem access, clipboard).

## Next Steps

1. Read the [Guidelines](/guidelines.md).
2. Complete a [Step By Step Guide](/publishing-tool/step-by-step-guide.md) tutorial.


---

# 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://lua2.fatality.win/workshop/getting-started.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.