Community Support
=================

This page describes where users should go when they need help with ``voiage``
and how the project wants support requests to be framed.

Support paths
-------------

The first stop for most questions should be the repository documentation:

* :doc:`../getting_started`
* :doc:`../cli_reference`
* :doc:`../examples/index`
* the binding walkthroughs in ``bindings/``

If the question is still unresolved, use the repository support surface:

* ``SUPPORT.md`` for general usage guidance
* the bug template for reproducible failures
* the feature template for roadmap-style requests
* ``SECURITY.md`` for private vulnerability reporting

What a good support request looks like
--------------------------------------

Support requests should be short, specific, and reproducible. Include:

* the ``voiage`` version
* the Python or binding runtime version
* the command or code snippet you ran
* the exact output you saw
* the output you expected

Support requests that lack a minimal reproducer are usually redirected to the
bug template or the relevant documentation page.

Community expectations
----------------------

The project keeps a pragmatic, technically focused support style:

* be respectful and direct
* keep the discussion scoped to the reported issue
* include enough context for another contributor to reproduce the behavior
* avoid asking for broad roadmap planning in support threads

The full community rules and security guidance live in the repository root:
``CODE_OF_CONDUCT.md`` and ``SECURITY.md``.