# Community and support

> Where to ask for help, how to ask a good question, and the distinction between community and commercial channels.

Source: https://crossfly.dev/docs/resources/community-and-support — CrossFly documentation. Full docs as one file: https://crossfly.dev/llms-full.txt

# Community and support

Stuck? Before asking, the **first stop** is self-help; then, the people channels.

## First stop (solves most cases)
1. [FAQ](/docs/faq/perguntas-frequentes) — common questions in 1–2 sentences.
2. [Troubleshooting](/docs/troubleshooting) — errors by symptom (compilation/runtime/render/build/platform).
3. [Reference](/docs/reference) — the exact signature.

## People channels
- **Community discussion** (forum/chat) — usage questions, patterns, feedback.
- **GitHub issues** — bugs and feature requests (with a minimal reproduction).
- **Commercial channels (Sovis, the maintainer)** — dedicated/commercial support, distinct from community
  support.

## How to ask a good question
Always include:
- The CrossFly **version** and **target platform** (desktop/Android/iOS/Web).
- The **`DebugConsole.txt`** (or the relevant log) — exceptions in callbacks are funneled through `Debug.handle`.
- An **MRE** (minimal reproducible example) — the smallest screen/snippet that reproduces the problem.
- What you **expected** vs. what **happened**.

> This speeds up the answer and avoids back-and-forth. Compilation errors after updating? It's probably the
> [2026 modernization](/docs/resources/changelog-whats-new) — check the [fix table](/docs/troubleshooting/compilation).

## See also
- [Changelog / What's new](/docs/resources/changelog-whats-new) · [Roadmap](/docs/resources/roadmap) · [Contributing](/docs/resources/contributing)