Migrate community and support content to mkdocs

content/community/index.md

@@ -5,4 +5,15 @@ hide:
   - navigation
 ---
 
-Placeholder
+Galasa thrives on users’ collaboration, contributions and creativity and we invite you to share your skills and ideas at all levels.
+
+Check out the [Contributing to Galasa guidelines](https://github.com/galasa-dev/projectmanagement/blob/main/contributing.md){target="_blank"} to propose fixes, add new features or improve the software and documentation.
+
+Join us on the [Open Mainframe Project Slack workspace](https://openmainframeproject.slack.com/archives/C05TCCQDE65){target="_blank"} where we discuss new features and provide support for each other.
+[Register to join](https://openmainframeproject.slack.com/signup#/domain-signup){target="_blank"} first if you're not yet a member.
+
+We have the following available Slack channels:
+
+- `#galasa-dev` - for developers of Galasa code or Galasa extensions 
+- `#galasa-users` - for users comments, and for making announcements 
+- `#galasa-tsc` - for technical steering committee discussions on longer term over-arching issues relating to Galasa 

content/support/index.md

@@ -5,4 +5,27 @@ hide:
   - navigation
 ---
 
-Placeholder
+If you find any problems whilst you’re using Galasa, get in touch and get the help you need:
+
+-	Search our [project management repository](https://github.com/galasa-dev/projectmanagement/issues){target="_blank"} on GitHub; perhaps someone has already had a similar issue and solved it.
+
+-  If you have an error message or java stack trace exception, feel free to raise an issue in the project management repository and the Galasa community will get back to you as soon as possible.
+
+-	Post a question in the [Open Mainframe Project Slack workspace](https://openmainframeproject.slack.com/archives/C05TCCQDE65){target="_blank"}.
+[Register to join](https://openmainframeproject.slack.com/signup#/domain-signup){target="_blank"} first if you're not yet a member.
+We have the following available Slack channels:
+
+    - `#galasa-dev` - for developers of Galasa code or Galasa extensions 
+    - `#galasa-users` - for users comments, and for making announcements 
+    - `#galasa-tsc` - for technical steering committee discussions on longer term over-arching issues relating to Galasa    
+
+
+If your issue requires a code change, the community will do their best to respond and fix the problem as soon as they can.
+Depending on the severity of the issue, the fix might be scheduled for a future release of Galasa.
+Alternatively, the fix might be back ported to the current release.
+Naturally this is always a community decision and your input is just as important.
+
+If you want to have a go at fixing the defect yourself, let us know and we will help you to try and fix the issue.
+
+We are open to suggestions about more formal support, come and talk to us - we would love to hear from you.
+