# Support
Thanks for using metadata-gen. Here is where to go for each kind of help.
## Questions & how-to
- **[Discussions](https://github.com/sebastienrousseau/metadata-gen/discussions)**
— usage questions, "how do I…", design ideas, and show-and-tell. This
is the best first stop and keeps answers searchable for others.
- **Docs** — [`README.md`](README.md), [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md),
[`DEVELOPMENT.md`](DEVELOPMENT.md), and the API docs on
[docs.rs/metadata-gen](https://docs.rs/metadata-gen).
## Bugs
Open an issue with the **Bug report** form. A minimal, self-contained
reproduction (the smallest front matter or HTML fragment and the exact
call) is the single most useful thing you can include — it usually
determines how fast a fix lands.
## Feature requests
Use the **Feature request** form. For anything touching the public API,
please float it in Discussions or the issue first so the rationale and
alternatives are captured before code is written.
## Security vulnerabilities
**Do not** open a public issue. Follow the private disclosure process in
[`SECURITY.md`](SECURITY.md). You'll get a prompt, confidential response.
## Versions & compatibility
- The library is in its `0.x` line: under Cargo's SemVer rules a patch
may carry breaking changes. Pin a specific `0.0.x` and read
[`CHANGELOG.md`](CHANGELOG.md) before upgrading.
- Minimum supported Rust version (MSRV): the `rust-version` in
`Cargo.toml`, enforced in CI.
## Response expectations
metadata-gen is maintained by a small team (currently one person) on a
best-effort basis — there is no paid support tier or response-time SLA
today. Clear, reproducible reports get triaged fastest. Please be patient
and kind; see the [Code of Conduct](CODE_OF_CONDUCT.md).