# Support

## Documentation and examples

Start with the [documentation](docs/index.md). It links to the getting started guide, interactive playground and focused examples for standalone editing, DataTables, Tabulator, inline editing and asynchronous selection.

See [compatibility](docs/reference/compatibility.md) for runtime and host requirements and the [changelog](CHANGELOG.md) for notable changes. Public exports are the supported integration boundary; source deep imports are not supported.

## Questions

Search the [existing issues](https://github.com/bensitu/omni-data-editor/issues) before opening a question. Describe what you are trying to achieve, the public API you are using and the behavior you expected. Include a small example when possible.

Support is community-based and depends on maintainer availability. No response-time or long-term support commitment is implied.

## Bug reports and feature requests

Use the repository's [issue templates](https://github.com/bensitu/omni-data-editor/issues/new/choose). A useful bug report includes the package version, runtime and browser versions, host versions when relevant, reproduction steps, and expected and actual behavior. Use synthetic data and remove credentials and personal information from examples and logs.

For feature requests, explain the user problem and how existing public APIs or extension points fall short. A concrete use case is more useful than a proposed implementation alone.

## Security and community concerns

Report vulnerabilities according to [SECURITY.md](SECURITY.md), using a private channel. Community participation follows the [code of conduct](CODE_OF_CONDUCT.md). Do not include confidential incident details in public support requests.