Deprecation notes added for exporters

Author: Elise-Kaminski

docs/porting/target/exporter.md

@@ -1,5 +1,7 @@
 # Porting a new target for exporters
 
+<span class="notes">**Note:** Note that exporters to export your code to various third party tools and IDEs are no longer supported. See this [blog post](https://os.mbed.com/blog/entry/Introducing-the-new-Mbed-Tools/) for more details.</span>
+
 Exporting allows users to transition from Mbed CLI to the development environment of their choice. When you add a new target, you must add support for exporters. The following sections explain how you add support for a new target to each exporter.
 
 ## Eclipse and Make

docs/program-setup/concepts/managed-unmanaged-bootloader.md

@@ -229,6 +229,8 @@ An unmanaged bootloader build is a method of controlling the link location of a
 
 ## Exporter limitations
 
+<span class="notes">**Note:** Note that exporters to export your code to various third party tools and IDEs are no longer supported. See this [blog post](https://os.mbed.com/blog/entry/Introducing-the-new-Mbed-Tools/) for more details.</span>
+
 Although the exporters can export bootloader projects using the bootloader parameters, there are some limitations.
 
 The exporters do not interpret Mbed OS configuration, and any changes to configuration parameters, especially bootloader parameters, require you to rerun the `mbed export` command.

docs/tools/mbed_cli_1/cli-create.md

@@ -37,6 +37,8 @@ You can create new applications as Mbed OS or non-versioned (blank) projects.
 
 When you create a new program, Mbed CLI automatically imports the latest [Mbed OS release](https://github.com/ARMmbed/mbed-os/). Each release includes all the components: code, build tools and IDE exporters.
 
+<span class="notes">**Note:** Note that exporters to export your code to various third party tools and IDEs are no longer supported. See this [blog post](https://os.mbed.com/blog/entry/Introducing-the-new-Mbed-Tools/) for more details.</span>
+
 With this in mind, let's create a new program (we'll call it `mbed-os-program`):
 
 ```

docs/tools/toolchains/export_to_third_party.md

@@ -1,5 +1,7 @@
 # Exporting
 
+<span class="notes">**Note:** Note that exporters to export your code to various third party tools and IDEs are no longer supported. See this [blog post](https://os.mbed.com/blog/entry/Introducing-the-new-Mbed-Tools/) for more details.</span>
+
 If you'd like to develop on Arm Mbed OS with a third party tool, or migrate to one, you can choose to export an Mbed project to the following development environments:
 
 - Keil µVision 5.0.

docs/tools/toolchains/exporters.md

@@ -1,5 +1,7 @@
 # About the exporters
 
+<span class="notes">**Note:** Note that exporters to export your code to various third party tools and IDEs are no longer supported. See this [blog post](https://os.mbed.com/blog/entry/Introducing-the-new-Mbed-Tools/) for more details.</span>
+
 Use the Arm Mbed exporters to export your code to various third party tools and IDEs. Each exporter implements a `generate` function that produces an IDE specific project file. Exporters benefit from Mbed build tools. However, instead of using your source and [config data](../build-tools/compile.html) to create an executable, we use that information to populate an IDE project file that will be configured to build, flash and debug your code.
 
 ## Arm Mbed CLI command

docs/tools/tools_intro.md

@@ -57,4 +57,6 @@ You can build Mbed OS with the Arm Compiler and GNU Arm Embedded toolchains. The
 
 ## Exporting to third party development tools
 
+<span class="notes">**Note:** Note that exporters to export your code to various third party tools and IDEs are no longer supported. See this [blog post](https://os.mbed.com/blog/entry/Introducing-the-new-Mbed-Tools/) for more details.</span>
+
 You can export your project from Mbed Studio or Mbed CLI to third party tools. For instructions, as well as tool-specific information, see the [Exporting to third party toolchains page](../build-tools/third-party-build-tools.html).