Merge pull request #732 from SignalK/discord

Replace mentions of Slack with Discord

README.md

@@ -169,4 +169,6 @@ For reference, the old SensESP version 1 documentation is still available at the
 
 ## Getting help
 
-Discussion about SensESP happens mostly in [Signalk-dev Slack](https://signalk-dev.slack.com/) on the #sensors channel. Don't hesitate to join (get invite via [signalk.org](https://signalk.org/)and ask if you ever have problems with getting your project working!
+Discussion about SensESP happens mostly on the [Signal K Discord](https://discord.com/channels/1170433917761892493/1170433918592368684) on the #sensesp channel. To register as a new user, follow the invite link at [signalk.org](https://signalk.org/).
+
+Another place for SensESP discussions is the [discussion board on the SensESP GitHub repository](https://github.com/SignalK/SensESP/discussions).

docs/pages/concepts/index.md

@@ -126,7 +126,7 @@ The two generic types of sensor data - [AnalogInput](https://signalk.org/SensESP
 
 Sensors for many specific types of physical sensors, like the BME280, or the SHT31, or the INAxxx, can be implemented by incorporating the relevant sensor library (often from Adafruit) and a few lines of code in `main.cpp`.
 
-Some specific sensors - for example, the MAX31856 thermocouple sensor - require a little more complex programming to read them, so they can be found [here](../additional_resources/). These "add-on" Sensor libraries can easily be included in a SensESP project by adding them to your `platformio.ini` file. If you have a physical sensor that you think fits in this category, and you want some help writing an add-on to read it, make a post in the #sensors channel on the Signalk-dev Slack.
+Some specific sensors - for example, the MAX31856 thermocouple sensor - require a little more complex programming to read them, so they can be found [here](../additional_resources/). These "add-on" Sensor libraries can easily be included in a SensESP project by adding them to your `platformio.ini` file. If you have a physical sensor that you think fits in this category, and you want some help writing an add-on to read it, make a post in the #sensesp channel on the Signal K Discord server.
 
 ## Transforms
 

docs/pages/contributing_code/index.md

@@ -22,7 +22,7 @@ If you like SensESP and want to make it even better, please do! It's written in
 
 - Do not commit PRs with internal merge commits. The information that you've merged changes from upstream at some point benefit no-one, probably not even you. You can avoid those merge commits by doing a `git pull --rebase upstream master` (or `git fetch` followed by `git rebase`, but that's more intricate) during your own work.
 
-- Normally, you should not need to modify `platformio.ini` for your PR. However, if you're adding code that requires a new library dependency, add the dependency both to `library.json` and `platformio.ini`. If you have questions, the best place to discuss SensESP is on [Slack](https://signalk-dev.slack.com), in the `#sensors` channel.
+- Normally, you should not need to modify `platformio.ini` for your PR. However, if you're adding code that requires a new library dependency, add the dependency both to `library.json` and `platformio.ini`. If you have questions, the best place to discuss SensESP is on [Signal K Discord Server](https://github.com/SignalK/SensESP/discussions), in the `#sensesp` channel.
 
 ## Write Comments That Create Interactive Documentation
 

docs/pages/get_in_touch/index.md

@@ -6,4 +6,4 @@ nav_order: 90
 
 # Get In Touch
 
-By far the best way to get in touch with someone who can help you with a SensESP issue is through the #sensors channel on the Signalk-dev Slack. If you're not already a member there (it's free), [start here](http://slack-invite.signalk.org/).
+By far the best way to get in touch with someone who can help you with a SensESP issue is through the #sensesp channel on the Signal K Discord Server. If you're not already a member there (it's free), follow the invite link on [signalk.org home page](https://signalk.org/).

docs/pages/troubleshooting/index.md

@@ -8,9 +8,9 @@ nav_order: 80
 
 A not-at-all-organized assortment of common problems and solutions.
 
-## Help on Slack
+## Help on Discord
 
-Slack is an online collaboration platform used by developers. You can join in the [Signal K discussion on Slack](https://signalk-dev.slack.com/) via [signalk.org][https://signalk.org]. The `#sensors` channel is the best place for you to ask questions about SensESP.
+Discord is an online messaging collaboration platform popular with open source projects. You can join the [Signal K Discord Server](https://discord.com/channels/1170433917761892493/1170433918592368684) via the invite link on [signalk.org][https://signalk.org]. The `#sensesp` channel is the best place for you to ask questions about SensESP.
 
 ## Missing Libraries
 
@@ -52,4 +52,3 @@ If the Pi is to be permanently connected to a network with an ethernet cable, yo
 12. When finished in Signal K, if the Pi is not connected to the network with an ethernet cable, you will probably need to undo all the changes you made above. Change everything back to how you found it in Step 3 above.
 
 (Thanks to @Graham Kendall for doing all the testing and documentation of the above!)
-