move android and custom integrations

content/en/building/features/integrations/_index.md

@@ -5,7 +5,7 @@ description: >
   Exchange data with other systems
 keywords: integrations interoperability
 relatedContent: >
-  building/guides/integrations
+  building/integrations
 aliases:
   - /apps/features/integrations/
 ---

content/en/building/features/integrations/openmrs.md

@@ -6,10 +6,9 @@ description: >
 keywords: openmrs
 relatedContent: >
   building/integrations/openmrs
-  building/features/integrations/custom
+  building/integrations/custom
   building/features/integrations/rapidpro
   building/features/integrations/dhis2
-  
 aliases:
    - /apps/features/integrations/openmrs
 ---

content/en/building/features/integrations/android.md → content/en/building/integrations/android.md

@@ -8,6 +8,7 @@ relatedContent: >
   building/reference/app-settings/assetlinks
 aliases:
    - /apps/features/integrations/android
+   - /building/features/integrations/android
 ---
 
 The [CHT Android application](https://github.com/medic/cht-android) can be launched by clicking on a link or invoking an intent in another Android app. This is useful for enabling login by SMS, directing a user to a specific page, and integrating between Android applications.

content/en/building/features/integrations/custom.md → content/en/building/integrations/custom.md

@@ -2,16 +2,16 @@
 title: "Custom"
 weight: 1
 description: >
-   Integrate with any system using RESTful APIs
+   Integrate the CHT with other systems using RESTful APIs
 keywords: generic, custom, integrations
-aliases:
-  -    /apps/features/integrations/generic/
 relatedContent: >
   building/features/integrations/dhis2
   building/features/integrations/rapidpro
   building/features/integrations/openmrs
 aliases:
    - /apps/features/integrations/custom
+   - /building/features/integrations/custom
+   - /apps/features/integrations/generic/
 ---
 
 The CHT Core Framework includes functionality that allows sharing data with any API-based system. Developers have configured CHT integrations with OpenMRS, KenyaEMR, Bahmni, DHIS2, RapidPro, Apache NiFi, OpenHIM, custom electronic medical records (EMR), and several other systems.  

content/en/building/integrations/openmrs.md

@@ -6,7 +6,7 @@ description: >
    Exchange patient-level data with systems based on the OpenMRS platform
 keywords: openmrs
 relatedContent: >
-  building/features/integrations/custom
+  building/integrations/custom
   building/features/integrations/openmrs
 aliases:
    - /apps/guides/integrations/openmrs
@@ -15,7 +15,7 @@ aliases:
 
 [OpenMRS](https://openmrs.org) is an open source electronic medical record system used in dozens of countries. Integrating CHT apps with OpenMRS can open up opportunities to improve health outcomes for patients by promoting better coordination of care. For example, referrals by CHWs in the community can be sent electronically to health facilities using OpenMRS so that nurses and clinicians can prepare for their visit and have full access to the assessment done by a CHW.
 
-Integrating CHT apps with OpenMRS can be achieved using the [OpenMRS REST API](https://rest.openmrs.org/) and following the guidance in the [Custom Integrations]({{< ref "building/features/integrations/custom" >}}) documentation. 
+Integrating CHT apps with OpenMRS can be achieved using the [OpenMRS REST API](https://rest.openmrs.org/) and following the guidance in the [Custom Integrations]({{< ref "building/integrations/custom" >}}) documentation. 
 
 ## Overview
 

content/en/building/reference/app-settings/assetlinks.md

@@ -5,7 +5,7 @@ weight: 5
 description: >
   **Assetlinks**: Defining the Digital Asset Links JSON file associating your domain with your Android app.
 relatedContent: >
-  building/features/integrations/android
+  building/integrations/android
   building/guides/android/branding
 keywords: android assetlinks
 aliases:
@@ -14,7 +14,7 @@ aliases:
 
 *Requires CHT Core 4.7.0+, CHT Conf 3.22.0+, and CHT Android 1.3.0+*
 
-When using a [custom flavor of cht-android]({{< ref "building/guides/android/branding" >}}) to connect to your CHT instance, the ecosystem supports using [deep links]({{< ref "building/features/integrations/android#sending-a-url" >}}) to open specific content in the app. (E.g. [token login links]({{< ref "building/concepts/access#magic-links-for-logging-in-token-login" >}})). Security measures in Android require these deep links [be verified](https://developer.android.com/training/app-links/verify-android-applinks) either automatically or manually.  This `assetlinks` configuration enables auto-verification for your CHT links in your Android app. The provided JSON file will be served at `https://<your CHT instance>/.well-known/assetlinks.json`. If you do not provide this configuration, users will be prompted to manually associate the CHT domain with your app.
+When using a [custom flavor of cht-android]({{< ref "building/guides/android/branding" >}}) to connect to your CHT instance, the ecosystem supports using [deep links]({{< ref "building/integrations/android#sending-a-url" >}}) to open specific content in the app. (E.g. [token login links]({{< ref "building/concepts/access#magic-links-for-logging-in-token-login" >}})). Security measures in Android require these deep links [be verified](https://developer.android.com/training/app-links/verify-android-applinks) either automatically or manually.  This `assetlinks` configuration enables auto-verification for your CHT links in your Android app. The provided JSON file will be served at `https://<your CHT instance>/.well-known/assetlinks.json`. If you do not provide this configuration, users will be prompted to manually associate the CHT domain with your app.
 
 For more information, see the [docs for building a new CHT Android flavor]({{< ref "building/guides/android/branding#android-app-links-verification" >}}).
 

content/en/exploring/covid-rdt-reference-app.md

@@ -93,7 +93,7 @@ Like all applications written for the CHT, there are built-in mechanisms to retr
  * **API Calls:** Given that all form submissions are captured in JSON and that we know the data model well, you can easily do API calls to a CHT server instance and use some custom code (node, python etc) to gather and show stats on a daily basis. You can export to either JSON or CSV. See API docs [for reports]({{< ref "building/reference/api#get-apiv2exportreports" >}}) as well as [monitoring metadata]({{< ref "building/reference/api#get-apiv2monitoring" >}}). 
  * **[PostgreSQL queries](https://github.com/medic/cht-sync):** CHT ships with a utility to export all the data that the API has to a relational database, Postgres. You have all the raw data the API has, but can now use the power of joins and groupings to come up with totally customizable stats by day, week, month etc. Data can be synched near real time from the CHT. 
  * **Dashboards:** Medic has used both [Klipfolio](https://www.klipfolio.com/) and, more recently, [Superset](https://superset.incubator.apache.org/) to create more complex yet still user-friendly dashboards. This is particular useful for those who need to view the data but wouldn't otherwise be logging in to CHT apps. These dashboards generally access the relational data in the Postgres database as the back end.
-  * **Third-Party Applications:** Connecting to third-party applications can be done using built-in [integrations]({{< ref "building/features/integrations" >}}), or building a workflow with [custom integrations]({{< ref "building/features/integrations/custom" >}}). 
+  * **Third-Party Applications:** Connecting to third-party applications can be done using built-in [integrations]({{< ref "building/features/integrations" >}}), or building a workflow with [custom integrations]({{< ref "building/integrations/custom" >}}). 
 
 
 ### Sample API call

content/en/exploring/learning-care.md

@@ -7,7 +7,7 @@ description: >
 keywords: oppia
 relatedContent: >
   building/features/integrations/oppia
-  building/guides/integrations/oppia
+  building/integrations/oppia
 aliases:
    - /apps/examples/learning-care
    - /building/examples/learning-care