# Development and contributing

Developing with Coordinator DB starts with a reproducible connection and a clear account of the behavior an application needs. This section covers public interfaces, integration checks and contributions to the examples and documentation that other developers use.

## Choose a starting point

* [Introduction](https://coordinatordb.com/docs/resources/develop-contribute/introduction/developer-instruction) explains how to prepare a small, reviewable change and select an interface.
* [Building](https://coordinatordb.com/docs/resources/develop-contribute/build/build) covers verification of an executable and its accompanying configuration on the intended machine.
* [Native protocol](https://coordinatordb.com/docs/resources/develop-contribute/native-protocol/protocol) describes the public native connection contract and the supplied client.
* [Contributing](https://coordinatordb.com/docs/resources/develop-contribute/contribute/tests) covers regression cases, reproducible checks and compatibility evidence.
* [Integration development](https://coordinatordb.com/docs/resources/develop-contribute/integrations) follows an adapter from interface selection to tests and documentation.
* [Roadmap](https://coordinatordb.com/docs/resources/develop-contribute/roadmap) explains how to distinguish documented behavior from a proposed capability.

Keep examples self-contained. Use sample data, include the selected database and output format, and state whether a check uses native TCP, HTTP or an embedded connection. Those choices affect sessions, transactions and parameter binding.

For the first connection, follow [installation](https://coordinatordb.com/docs/get-started/setup/install). For an existing application, begin with [deployment modes](https://coordinatordb.com/docs/get-started/about/deployment-modes).
