<commit_before>---
layout: sidebar_toc
title: Contribute 
sidebar_toc:
  - url: '#development'
    name: 'Core Development'
  - url: '#plugins'
    name: 'Plugins'
  - url: '#udos'
    name: 'User-defined Opcodes'
  - url: '#documentation'
    name: 'Documentation'
  - url: '#website'
    name: 'Website'
  - url: '#community'
    name: 'Community'
---
<h2 id="development">Core Development</h2>

<h2 id="plugins">Plugins</h2>

<h2 id="udos">User-Defined Opcodes</h2>

<h2 id="documentation">Documentation</h2>

<h2 id="website">Website</h2>

The Csound website you are currently viewing is itself an open-source project. The site is generated using the Jekyll templating system, and the source code is available online at [http://www.github.com/csound/csound.github.io](http://www.github.com/csound/csound.github.io).  The project contains a [http://www.github.com/csound/csound.github.io/blob/master/README.md](README.md) that explains how the site is generated and how users can modify and test the site locally.

Users have a number of options for contributing to the site:

1. Report issues to the site's [http://www.github.com/csound/csound.github.io](issue tracker).  This could be things like typos in text, reports on pages that could be improved, reports of broken or updated links, suggestions for additional text, requests for news to be posted, etc. Using the issue tracker allows the site maintainers to discuss the issue with the issue's author and with each other to ensure that the issue is satisfactorily addressed. 
2. Discuss on the Csound Users Mailing List any of the above.  Most of the site maintainers are active readers of the Csound Mailing list and can either address the site changes directly or work on getting a new issue filed and addressed.
3. Users with technical understanding of Github and Jekyll can fork the project, make changes to their version of the project, then submit pull requests.  Site maintainers will work to process all pull requests quickly. 

If you are interested to contribute time to help maintain and improve the website, please contact one of the existing site maintainers and we can arrange for you to join the site maintenance group in Github.  This will allow direct commits to this repository. 

<h2 id="website">Community</h2><commit_msg>[fix] links on the contribute page #50<commit_after>---
layout: sidebar_toc
title: Contribute 
sidebar_toc:
  - url: '#development'
    name: 'Core Development'
  - url: '#plugins'
    name: 'Plugins'
  - url: '#udos'
    name: 'User-defined Opcodes'
  - url: '#documentation'
    name: 'Documentation'
  - url: '#website'
    name: 'Website'
  - url: '#community'
    name: 'Community'
---
<h2 id="development">Core Development</h2>

<h2 id="plugins">Plugins</h2>

<h2 id="udos">User-Defined Opcodes</h2>

<h2 id="documentation">Documentation</h2>

<h2 id="website">Website</h2>

The Csound website you are currently viewing is itself an open-source project. The site is generated using the Jekyll templating system, and the source code is available online at [https://github.com/csound/csound.github.io](https://github.com/csound/csound.github.io). The project contains a [README.md](https://github.com/csound/csound.github.io/blob/master/README.md) that explains how the site is generated and how users can modify and test the site locally.

Users have a number of options for contributing to the site:

1. Report issues to the site's [issue tracker](https://github.com/csound/csound.github.io/issues).  This could be things like typos in text, reports on pages that could be improved, reports of broken or updated links, suggestions for additional text, requests for news to be posted, etc. Using the issue tracker allows the site maintainers to discuss the issue with the issue's author and with each other to ensure that the issue is satisfactorily addressed. 
2. Discuss on the Csound Users Mailing List any of the above.  Most of the site maintainers are active readers of the Csound Mailing list and can either address the site changes directly or work on getting a new issue filed and addressed.
3. Users with technical understanding of Github and Jekyll can fork the project, make changes to their version of the project, then submit pull requests.  Site maintainers will work to process all pull requests quickly. 

If you are interested to contribute time to help maintain and improve the website, please contact one of the existing site maintainers and we can arrange for you to join the site maintenance group in Github.  This will allow direct commits to this repository. 

<h2 id="website">Community</h2>
{'fraction_non_alphanumeric': 0.08263032662773091, 'fraction_numerical': 0.006921912178239239, 'mean_word_length': 4.333333333333333, 'pattern_counts': {'":': 0, '<': 27, '<?xml version=': 0, '>': 27, 'https://': 4, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6108372', 'n_tokens_mistral': 1295, 'n_tokens_neox': 1250, 'n_words': 603}