IGAPP-333: Move and adjust commonly used docs

docs/build-configs.md

@@ -12,7 +12,7 @@ We use the concept of build configs to build different versions of the app. A bu
 * **integreat**: Build config for Integreat using the production integreat cms.
 * **malte**: Build config for the Malte app which uses a different design, name and cms.
 * **integreat-test-cms**: Build config for development using the test cms and with additional features enabled.
-* **integreat-e2e**: Build config for [E2E-Tests](native/docs/e2e-testing.md), primarily used in the [CI](docs/cicd.md).
+* **integreat-e2e**: Build config for [E2E-Tests](native/docs/e2e-testing.md), primarily used in the [CI](cicd.md).
 
 **NOTE: Testing and developing with the live cms instance should be avoided. Therefore, the `integreat-test-cms` build config should be used primarily.**
 
@@ -24,3 +24,7 @@ See the corresponding sections for [native](native/docs/build-configs.md#using-a
 
 Each build config is a set of javascript files (possibly including common files) that can be found in the [corresponding directory](../build-configs/configs).
 See the corresponding sections for [native](native/docs/build-configs.md#technical-information) and [web](web/docs/build-configs.md#technical-information).
+
+## Whitelabelling
+
+If you want to add more build configs in order to create a new whitelabelled app, have a look at the [whitellabelling docu](whitelabelling.md).

docs/contributing.md

@@ -19,6 +19,8 @@ Other team members you can contact are
 
 ## Pull requests
 
+**Testing with the live cms instance should be avoided. Instead, [please use the test cms](docs/technology-stack.md#test-cms).**
+
 Before starting to write code and opening a pull request, please take a look [at our conventions](docs/conventions.md).
 
 Pull requests should always belong to an [issue in our issue tracker](#bug-reporting).
@@ -45,5 +47,7 @@ They are also shown in the stores and the [release section of github](https://gi
 
 ## Bug reporting
 
+**Testing with the live cms instance should be avoided. Instead, [please use the test cms](docs/technology-stack.md#test-cms).**
+
 You can [view our issues](https://issues.integreat-app.de/projects/NATIVE) or
 [create new ones](https://issues.integreat-app.de/secure/CreateIssue!default.jspa) on our jira.

native/docs/whitelabelling.md → docs/whitelabelling.md

@@ -93,7 +93,10 @@ Things the AppTeam has to do and therefore probably create issues for.
     * Android
     * iOS
 * Add sentry flag
-* Create screenshots
+* Create screenshots with the following aspect ratios (for iOS):
+    * 1242 x 2208
+    * 1242 x 2688
+    * 2048 x 2732
 * Add to google search console
 * Translate and add locales
     * New languages

native/docs/technical-documentation.md

@@ -9,7 +9,6 @@
 * [I18n](docs/i18n.md)
 * [Error reporting](docs/error-reporting.md)
 * [React Native Upgrades](docs/react-native-upgrades.md)
-* [Whitelabelling](docs/whitelabelling.md)
 
 ## Technology Stack
 

native/docs/troubleshooting.md

@@ -107,4 +107,4 @@ More information on how to set the environment variable can be found [here](buil
 ## Invalid BUILD_CONFIG_NAME supplied
 
 Invalid environment variable `BUILD_CONFIG_NAME` set before running the packager.
-All available build configs can be found [here](build-configs.md#available-build-configs).
+All available build configs can be found [here](../../docs/build-configs.md#available-build-configs).