Remove Mendix 8 documentation

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-8/pluggable-widgets/differences-between-pluggable-and-custom-widgets.md

@@ -7,13 +7,13 @@ description: This document explains the differences between pluggable and custom
 
 ## Introduction
 
-Pluggable widgets are the successor to [Custom widgets](/howto8/extensibility/widget-development/). Pluggable widgets are based on a modern React framework, have access to better APIs in the client, and can use more advanced properties in Studio Pro. Therefore, pluggable widgets allow you to more easily implement existing front-end libraries, tools, and your own expertise. Pluggable widgets should be used instead of custom widgets whenever possible.
+Pluggable widgets are based on a modern React framework, have access to better APIs in the client, and can use more advanced properties in Studio Pro. Therefore, pluggable widgets allow you to more easily implement existing front-end libraries, tools, and your own expertise. Pluggable widgets should be used instead of custom widgets whenever possible.
 
 ## Differences Between Pluggable and Custom Widgets
 
 | Concept      | Pluggable widgets                                                                                     | Custom widgets                                                           |
 | ------------ | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
-| Framework    | [React](/apidocs-mxsdk/apidocs/pluggable-widgets/#client-component)                                                                         | [Dojo](/howto8/extensibility/widget-development/#dojo)                 |
+| Framework    | [React](/apidocs-mxsdk/apidocs/pluggable-widgets/#client-component)                                                                         | Dojo                 |
 | Data access  | Declarative, props-based                                                                              | Imperative, callback-based                                               |
 | Data updates | [Receive updates in props](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#dynamic-value) | [Subscribe](https://apidocs.rnd.mendix.com/8/client/mx.data.html#.subscribe) |
 | API          | [Pluggable widgets API](/apidocs-mxsdk/apidocs/pluggable-widgets/)                                     | [Mendix Client API](/apidocs-mxsdk/apidocs/client-api/)                |

content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md

@@ -276,7 +276,7 @@ Do not use "Mendix Administrator."
 
 This term replaces "Mendix" and "Mendix Mobile app" (which are not to be used in the product UI or documentation).
 
-Always use "the Mendix Developer App" and cross-reference [Getting the Mendix Developer App](/refguide8/getting-the-mendix-app/) where possible.
+Always use "the Mendix Developer App" and cross-reference [Getting the Mendix Developer App](/refguide/getting-the-mendix-app/) where possible.
 
 ### Mendix Client
 

content/en/docs/deployment/mobileapp.md

@@ -19,8 +19,6 @@ This page is divided into three tabs:
 {{% alert color="warning" %}}
 Building hybrid apps in the cloud uses the PhoneGap Build service from Adobe. Because Adobe no longer maintains this service, building hybrid apps in the cloud and publishing them to app stores is no longer possible.
 
-To build a hybrid app and publish it, see [How to Build a Mendix Hybrid App Locally](/howto8/mobile/build-hybrid-locally/) for information on local building.
-
 To publish your app in an app store, Mendix recommends building native iOS apps instead. For more information, see [Build Native Apps](/refguide/mobile/distributing-mobile-apps/building-native-apps/).
 {{% /alert %}}
 
@@ -94,9 +92,9 @@ Take note of the required resolutions and file types for the image files, as the
 
 Once you begin the app building wizard and choose the correct environment, click **Download a customizable package**. The package contains all your settings, icons, and splash screens. It allows you to easily make changes, create local builds, and run on emulators.
 
-For iOS please follow the instructions in the [Building Your iOS App Locally](/howto8/mobile/build-hybrid-locally/#building-ios-locally) section of *How to Build a Mendix Hybrid App Locally*.
+For iOS, follow the instructions in the [Building an iOS App with Xcode](/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/#building-ios-app) section of *Build a Mendix Native App Locally*.
 
-For Android please follow the instructions in the [Building Your Android App Locally](/howto8/mobile/build-hybrid-locally/#building-android-locally) section of *How to Build a Mendix Hybrid App Locally*.
+For Android, follow the instructions in the [Building an Android App with Android Studio](/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/#building-android-app) section of *Build a Mendix Native App Locally*.
 
 ## Read More
 

content/en/docs/deployment/on-premises-design/buildpacks/cloud-foundry-deploy.md

@@ -7,12 +7,10 @@ aliases:
     - /deployment/cloud-foundry/index.html
     - /howto/deploying-a-mendix-app-to-cloud-foundry.html
     - /refguide/deploying-a-mendix-app-to-cloud-foundry.html
-    - /refguide8/deploying-a-mendix-app-to-cloud-foundry.html
     - /refguide9/deploying-a-mendix-app-to-cloud-foundry.html
     - /deployment/cloud-foundry/
     - /howto/deploying-a-mendix-app-to-cloud-foundry
     - /refguide/deploying-a-mendix-app-to-cloud-foundry
-    - /refguide8/deploying-a-mendix-app-to-cloud-foundry 
     - /refguide9/deploying-a-mendix-app-to-cloud-foundry
     - /developerportal/deploy/cloud-foundry-deploy/
 #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps.

content/en/docs/howto/front-end/atlas-ui/get-started/_index.md

@@ -10,8 +10,6 @@ This section explains Atlas and how developers can get started with the Atlas UI
 
 The Atlas UI framework enables all types of developers to build consistent and beautiful apps. Developers can use the default look and feel, they can slightly customize it, and use Atlas to create a fully tailored re-usable design across all your apps.
 
-Atlas 2 corresponds with Mendix 8. If you need information on Atlas 2, see the Mendix 8 how-to documentation for [Atlas 2](/howto8/front-end/atlas-ui/).
-
 ## Design Principles
 
 Atlas UI has a philosophy based on the core principles described below. These principles guide all our design decisions at Mendix, and we encourage every Mendix user to adopt them when building their own apps.

content/en/docs/howto10/front-end/atlas-ui/get-started/_index.md

@@ -10,8 +10,6 @@ This section explains Atlas and how developers can get started with the Atlas UI
 
 The Atlas UI framework enables all types of developers to build consistent and beautiful apps. Developers can use the default look and feel, they can slightly customize it, and use Atlas to create a fully tailored re-usable design across apps.
 
-Atlas 2 corresponds with Mendix 8. If you need information on Atlas 2, see the Mendix 8 how-to documentation for [Atlas 2](/howto8/front-end/atlas-ui/).
-
 ## Design Principles
 
 Atlas UI has a philosophy based on the core principles described below. These principles guide all our design decisions at Mendix, and we encourage every Mendix user to adopt them when building their own apps.