Removed BUILD.md from master as source now lives in gh-pages (#6709)

CONTRIBUTING.md

@@ -38,7 +38,7 @@ For making changes to the Windows Machine Learning WinRT API, please label your
 * A feature can be implemented by you, the ONNX Runtime team, or other community members.  Code contributions are greatly appreciated: feel free to work on any reviewed feature you proposed, or choose one in the backlog and send us a PR. If you are new to the project and want to work on an existing issue, we recommend starting with issues that are tagged with “good first issue”. Please let us know in the issue comments if you are actively working on implementing a feature so we can ensure it's assigned to you.  
 * Unit tests: New code *must* be accompanied by unit tests.
 * Documentation and sample updates: If the PR affects any of the documentation or samples then include those updates in the same PR.
-* Build instructions are [here](BUILD.md).
+* Build instructions are [here](https://www.onnxruntime.ai/docs/how-to/build.html).
 * Checkin Procedure:  Once a feature is complete and tested according to the contribution guidelines follow these steps:
    * Fork the repo
    * git clone your fork

docs/Android_testing.md

@@ -1,6 +1,6 @@
 # Testing Android Changes using the Emulator
 
-See [BUILD.md](../Build.md#Android) for Android build instructions and information on the locations of the various files referred to here. 
+See [Android build instructions](https://www.onnxruntime.ai/docs/how-to/build.html#android) and information on the locations of the various files referred to here.
 
 ## Install the emulator
 

docs/ONNX_Runtime_Server_Usage.md

@@ -101,7 +101,7 @@ For easy tracking of requests, we provide the following header fields:
 
 ### rsyslog Support
 
-If you prefer using an ONNX Runtime Server with [rsyslog](https://www.rsyslog.com/) support([build instruction](../BUILD.md#build-onnx-runtime-server-on-linux)), you should be able to see the log in `/var/log/syslog` after the ONNX Runtime Server runs. For detail about how to use rsyslog, please reference [here](https://www.rsyslog.com/category/guides-for-rsyslog/).
+If you prefer using an ONNX Runtime Server with [rsyslog](https://www.rsyslog.com/) support([build instruction](https://www.onnxruntime.ai/docs/how-to/build.html#build-onnx-runtime-server-on-linux)), you should be able to see the log in `/var/log/syslog` after the ONNX Runtime Server runs. For detail about how to use rsyslog, please reference [here](https://www.rsyslog.com/category/guides-for-rsyslog/).
 
 ## Report Issues
 

docs/Reduced_Operator_Kernel_build.md

@@ -6,7 +6,7 @@ A configuration file must be created with details of the kernels that are requir
 
 Following that, ORT must be manually built, providing the configuration file in the `--include_ops_by_config` parameter. The build process will update the ORT kernel registration source files to exclude the unused kernels. 
 
-See the [build instructions](https://github.com/microsoft/onnxruntime/blob/master/BUILD.md#build-instructions) for more details on building ORT.
+See the [build instructions](https://www.onnxruntime.ai/docs/how-to/build.html#build-instructions) for more details on building ORT.
 
 When building ORT with a reduced set of kernel registrations, `--skip_tests` **MUST** be specified as the kernel reduction will render many of the unit tests invalid. 
 

docs/python/notebooks/onnxruntime-nuphar-tutorial.ipynb

@@ -17,7 +17,7 @@
     "\n",
     "This example shows how to accelerate model inference using Nuphar, an execution provider that leverages just-in-time compilation to generate optimized executables.\n",
     "\n",
-    "For more background about Nuphar, please check [Nuphar-ExecutionProvider.md](https://github.com/microsoft/onnxruntime/blob/master/docs/execution_providers/Nuphar-ExecutionProvider.md) and its [build instructions](https://github.com/microsoft/onnxruntime/blob/master/BUILD.md#nuphar).\n",
+    "For more background about Nuphar, please check [Nuphar-ExecutionProvider.md](https://github.com/microsoft/onnxruntime/blob/master/docs/execution_providers/Nuphar-ExecutionProvider.md) and its [build instructions](https://www.onnxruntime.ai/docs/how-to/build.html#nuphar).\n",
     "\n",
     "#### Tutorial Roadmap:\n",
     "1. Prerequistes\n",

java/README.md

@@ -10,7 +10,7 @@ For general purpose usage of the publicly distributed API, please see the [gener
 
 ### Building
 
-Use the main project's [build instructions](../BUILD.md) with the `--build_java` option.
+Use the main project's [build instructions](https://www.onnxruntime.ai/docs/how-to/build.html) with the `--build_java` option.
 
 #### Requirements
 

nodejs/README.md

@@ -28,7 +28,7 @@ Following platforms are supported with pre-built binaries:
 - Linux x64 CPU NAPI_v3
 - MacOS x64 CPU NAPI_v3
 
-To use on platforms without pre-built binaries, you can build Node.js binding from source and consume it by `npm install <onnxruntime_repo_root>/nodejs/`. See also [BUILD.MD](../BUILD.md#apis-and-language-bindings) for building ONNX Runtime Node.js binding locally.
+To use on platforms without pre-built binaries, you can build Node.js binding from source and consume it by `npm install <onnxruntime_repo_root>/nodejs/`. See also [instructions](https://www.onnxruntime.ai/docs/how-to/build.html#apis-and-language-bindings) for building ONNX Runtime Node.js binding locally.
 
 ## License
 

samples/c_cxx/README.md

@@ -15,7 +15,7 @@ This directory contains a few C/C++ sample applications for demoing onnxruntime
 You may get a precompiled libpng library from [https://onnxruntimetestdata.blob.core.windows.net/models/libpng.zip](https://onnxruntimetestdata.blob.core.windows.net/models/libpng.zip)
 
 ## Install ONNX Runtime
-You may either get a prebuit onnxruntime from nuget.org, or build it from source by following the [build instructions](../../BUILD.md). 
+You may either get a prebuit onnxruntime from nuget.org, or build it from source by following the [build instructions](https://www.onnxruntime.ai/docs/how-to/build.html).
 If you build it by yourself, you must append the "--build_shared_lib" flag to your build command. 
 Open Developer Command Prompt for Visual Studio version you are going to use. This will setup necessary environment for the compiler and other things to be found.
 ```