Contributing to CollectiveAccess

There are many ways to contribute to CollectiveAccess.

Support and documentation​

You can help other community members by posting to the support forum or responding in the community Gitter chat.

Alternatively, expanding or improving this documentation will help too! If you aren't familiar with markdown (which is used to write pages) you can still offer suggestions or documentation improvements via the issue tracker.

More technical documentation contributors can directly edit CollectiveAccess' documentation repository - see the README.md which describes the technical aspects.

Localisation / Translation​

Translations of CollectiveAccess Providence and Pawtucket are done with Transifex. See the translation page for more information on the process.

CollectiveAccess documentation is not currently localisable but may be in future.

Reporting problems​

If you've found a problem or have an enhancement suggestion post an issue on Providence or Pawtucket's GitHub issues page.

Development​

Developers can join the developer Slack channel, a venue for developer discussion and support.

For those with fixes to contribute a pull request to Providence or Pawtucket GitHub repositories is always appreciated!