added module sharing information

1 files changed, 2 insertions, 2 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2235195..e2e8df0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -27,7 +27,7 @@ While developing, you **_should_**:
 
 On the other hand, you **_should not_**:
 
-1. **Commit _any_ modules to the _jasper-client_ repository.** The modules included in _jasper-client_ are meant as illustrative examples. Any new modules that you'd like to share should be done so through other means. There should be a separate _modules_ repository around in the near future.
+1. **Commit _any_ modules to the _jasper-client_ repository.** The modules included in _jasper-client_ are meant as illustrative examples. Any new modules that you'd like to share should be done so through other means. If you'd like us to [list your module](http://jasperproject.github.io/documentation/modules/) on the web site, [submit a pull request here](https://github.com/jasperproject/jasperproject.github.io/blob/master/documentation/modules/index.md).
 2. **_Not_ do any of the DOs!**
 
 ## TODOs
@@ -39,4 +39,4 @@ If you're looking for something to do, here are some suggestions:
 3. Buff up the text-refinement functions in [`alteration.py`](https://github.com/jasperproject/jasper-client/blob/master/client/alteration.py). These are meant to convert text to a form that will sound more human-friendly when spoken by your TTS software, but are quite minimal at the moment.
 4. Make Jasper platform-independent (this is a big one). For example, allow Jasper to run on OS X.
 5. Decouple Jasper from any specific Linux audio driver implementation.
-6. Modularize the speech-to-text and text-to-speech system so that Jasper developers can swap in their own implementations. This would allow some users to plug in, for example, the AT&T speech-to-text service while avoiding an inherent dependence (for Jasper core) on a third-party web service.
\ No newline at end of file
+6. Modularize the speech-to-text and text-to-speech system so that Jasper developers can swap in their own implementations. This would allow some users to plug in, for example, the AT&T speech-to-text service while avoiding an inherent dependence (for Jasper core) on a third-party web service.