Merge pull request #3752 from plentymarkets/fix/readme_and_contribution_guide

removed mentions of the old forum and fixed some links

Author: Tim-M-S

README.md

@@ -26,22 +26,18 @@ Your Javascript, widget and SCSS changes have now been assembled locally.
 ## Plugin documentation
 
 - Learn how to create your [first plentymarkets plugin](https://developers.plentymarkets.com/tutorials/helloworld)
-- Installing a [template](https://developers.plentymarkets.com/tutorials/design)
+- Installing a [template](https://developers.plentymarkets.com/en-gb/developers/main/plentyshop-plugins/template-setup.html)
 - Developing [template plugins](https://developers.plentymarkets.com/dev-doc/template-plugins)
 - The plentymarkets [plugin interface](https://developers.plentymarkets.com/dev-doc/basics#introduction-interface)
-- The plentymarkets [REST API](https://developers.plentymarkets.com/rest-doc/introduction)
-
-## Join our community
-
-Sign up today and become a member of our [forum](https://forum.plentymarkets.com/c/plugin-entwicklung). Discuss the latest trends in plugin development and share your ideas with our community.
+- The plentymarkets [REST API](https://developers.plentymarkets.com/en-gb/developers/main/rest-api-guides/getting-started.html)
 
 ## Contribute to the project 
 
 If you want to contribute to our open source projects, you can learn how to open pull requests in our [Contribution guide](https://github.com/plentymarkets/plugin-ceres/blob/stable/contributionGuide.md).
 
 ## Versioning
 
-Visit our forum and find the latest news and updates in our [Changelog](https://forum.plentymarkets.com/c/changelog?order=created).
+Find the latest news and updates in our [Changelog](https://github.com/plentymarkets/plugin-ceres/releases).
 
 ## License
 

contributionGuide.md

@@ -13,7 +13,7 @@ Thanks a lot for being a part of our community!
 Whether you're planning to contribute a feature or fix a bug, we will have to assess your code and decide whether or not we can include it in a future release. We don't want you to invest a lot of time and effort into a contribution that we cannot accept. However, there are certain limitations to which contributions we can implement: In some cases, internal dependencies to the PlentyONE core may impede the inclusion of a feature; in other cases, our LTS (long-term support)
 promise for plentyShop LTS 5.0.X prevents us from accepting your contribution, because it may lead to breaking changes for external plugins.
 
-That is why you should talk to us before you begin working on a larger contribution to plentyShop LTS. Just open a new thread [in the plentyShop category in the forum](https://forum.plentymarkets.com/c/plentyshop/). Tag the new post with the tag **Contribution**. Briefly explain what you're planning to do and how you would go about. Our developers will have a look at your input and contact you to discuss whether it's possible or not.
+That is why you should talk to us before you begin working on a larger contribution to plentyShop LTS.
 
 ## Which contributions will not be accepted?
 
@@ -25,9 +25,9 @@ It's hard to say. Mainly, we reserve the right to reject your contribution if:
 
 ## Contributing bug fixes
 
-If you want to help improve plentyShop LTS by contributing bug fixes, you can find a list of all currently known bugs in the [issues column on GitHub](https://github.com/plentymarkets/plugin-ceres/issues). Each individual entry on the issues board includes a link to the corresponding thread in the forum, if you need further information.
+If you want to help improve plentyShop LTS by contributing bug fixes, you can find a list of all currently known bugs in the [issues column on GitHub](https://github.com/plentymarkets/plugin-ceres/issues).
 
-If you find a bug that's not on the GitHub issues board, let us know by opening a new thread [in the plentyShop category in the forum](https://forum.plentymarkets.com/c/plentyshop/). Include detailed information on how to reproduce the bug. This includes:
+Include detailed information on how to reproduce the bug. This includes:
 
 - the plugin version(s) in which the bug appears
 - the browser(s) you're using and its version
@@ -55,9 +55,9 @@ While we're always striving to improve the code documentation in the project, th
 9. Mention **@plentymarkets-plentyshop** in the description of your pull request.
 10. Add a few sentences that describe the changes you've made in the description of the pull request.
 
-After you've opened a pull requests, the PR will be subject to our automated tests. If one or more of the checks is failing, please consider the proposed adjustments to your pull request. If it's unclear why the test failed, make sure to contact us either by mentioning **@plentymarkets-plentyshop** in the PR's conversation or by opening a new thread in the forum. 
+After you've opened a pull requests, the PR will be subject to our automated tests. If one or more of the checks is failing, please consider the proposed adjustments to your pull request. If it's unclear why the test failed, make sure to contact us by mentioning **@plentymarkets-plentyshop** in the PR's conversation.
 
-If your contribution requires additional documentation on our part, please also mention GitHub user **fmutschler** in the PR conversation or user **franz.mutschler** in the forum.
+If your contribution requires additional documentation on our part, please also mention GitHub user **fmutschler** in the PR conversation.
 
 ## Branch naming