diff --git a/docs/media/vscode_presets_toolbar.png b/docs/media/vscode_presets_toolbar.png
new file mode 100644
index 0000000..7b58ce4
--- /dev/null
+++ b/docs/media/vscode_presets_toolbar.png
Binary files differ
diff --git a/docs/media/vsode_enable_preset.png b/docs/media/vsode_enable_preset.png
new file mode 100644
index 0000000..2f77b67
--- /dev/null
+++ b/docs/media/vsode_enable_preset.png
Binary files differ
diff --git a/docs/sections/building.md b/docs/sections/building.md
index 6be51be..34c78c6 100644
--- a/docs/sections/building.md
+++ b/docs/sections/building.md
@@ -19,7 +19,7 @@
     - [Configuring the build for MPS3 SSE-310](./building.md#configuring-the-build-for-mps3-sse_310)
     - [Configuring native unit-test build](./building.md#configuring-native-unit_test-build)
     - [Configuring the build for simple-platform](./building.md#configuring-the-build-for-simple_platform)
-    - [Building with CMakePresets](./building.md#building-with-cmakepresets)
+    - [Building with CMake Presets](./building.md#building-with-cmake-presets)
     - [Building the configured project](./building.md#building-the-configured-project)
   - [Building timing adapter with custom options](./building.md#building-timing-adapter-with-custom-options)
   - [Add custom inputs](./building.md#add-custom-inputs)
@@ -588,66 +588,9 @@
     -DCMAKE_TOOLCHAIN_FILE=scripts/cmake/toolchains/bare-metal-armclang.cmake
 ```
 
-### Building with CMakePresets
+### Building with CMake Presets
 
-If you are using CMake version 3.23.3 or above, then an alternative method of building is by using CMakePresets.
-CMakePresets are well supported by most IDEs and serve as a developer-convenience tool.
-Presets can be also used from a command-line:
-```commandline
-cmake --preset <config-name>
-cmake --build --preset <config-name>
-```
-where config-name is one of:
-```commandline
-native
-mps3-300-gcc
-mps3-300-clang
-mps3-310-gcc
-mps3-310-clang
-simple-gcc
-simple-clang
-```
-This will automatically configure and build the evaluation-kit into a corresponding folder.
-You can still pass in build flags as usual, for example:
-```commandline
-cmake --preset mps3-300-gcc -DUSE_CASE_BUILD=inference_runner
-cmake --build --preset mps3-300-gcc
-```
-Alternatively, you can create a CMakeUserPresets.json in the root of the project with personal user settings, for example:
-```commandline
-{
-  "version": 3,
-  "cmakeMinimumRequired": {
-    "major": 3,
-    "minor": 21,
-    "patch": 0
-  },
-  "configurePresets": [
-    {
-      "name": "my-config",
-      "displayName": "my-config",
-      "inherits": ["mps3-300-gcc"],
-      "cacheVariables": {
-        "LOG_LEVEL": {
-          "type": "STRING",
-          "value": "LOG_LEVEL_DEBUG"
-        }
-      }
-    }
-  ],
-  "buildPresets": [
-    {
-      "name": "mps3-300-gcc-custom",
-      "displayName": "mps-300-gcc-custom",
-      "configurePreset": "my-config",
-      "targets": [
-        "ethos-u-object_detection",
-        "ethos-u-inference_runner"],
-      "jobs": 12
-    }
-  ]
-}
-```
+For building using CMake Presets please see [Building with CMake Presets](./cmake_presets.md)
 
 ### Building the configured project
 
diff --git a/docs/sections/cmake_presets.md b/docs/sections/cmake_presets.md
new file mode 100644
index 0000000..cff5329
--- /dev/null
+++ b/docs/sections/cmake_presets.md
@@ -0,0 +1,85 @@
+# Building with CMake Presets
+
+If you are using CMake version 3.23.3 or above, then an alternative method of building is by using CMake Presets.
+
+## Using presets with Visual Studio Code (VS Code)
+
+CMake Presets are well supported by most IDEs and serve as a developer-convenience tool. This section would demonstrate the use of CMake Presets in VS Code.
+In order to use CMake Presets in VS Code the [CMake Tools extension](https://code.visualstudio.com/docs/cpp/cmake-linux) has to be installed and *Use Cmake Presets* option has to be turned to either *always* or *auto*.
+![Make VS Code use presets](../media/vsode_enable_preset.png)
+For further information on how to enable the use of CMake and presets in VS Code please refer to [VS Code CMake Tools documentation](https://github.com/microsoft/VSCode-cmake-tools/blob/main/docs/cmake-presets.md).
+
+Once the presets are enabled in VS Code and the root folder of the project is opened in the editor - VS Code should automatically find the `CMakePresets.json` (or `CMakeUserPresets.json`) in the root folder and parse them accordingly.
+From that point user can switch between configurations and build the selected preset using the toolbar at the bottom of the editor:
+![VS Code build and preset toolbar](../media/VS Code_presets_toolbar.png)
+The project provides basing configuration and build presets along with one CTest test preset (for native platform only). Each configuration preset has only one build preset. All build presets have different use-cases listed as targets for user convenience.
+
+It is encouraged to create a personal `CMakeUserPreset.json` with personal user presets that are based on the provided default presets. User's preset file automatically includes the default preset file. An example of such a user preset can be find below:
+```
+{
+    "version": 4,
+    "cmakeMinimumRequired": {
+        "major": 3,
+        "minor": 23,
+        "patch": 0
+    },
+    "configurePresets": [
+        {
+            "name": "example-user-preset",
+            "displayName": "My config simple-gcc",
+            "description": "This preset uses public presets available in this repository.",
+            "inherits": [
+                "simple-gcc",
+                "log-debug",
+                "single-input"
+            ]
+        }
+    ],
+    "buildPresets": [
+        {
+            "name": "build-kws",
+            "displayName": "kws",
+            "configurePreset": "example-user-preset",
+            "jobs": 8,
+            "targets": [
+                "ethos-u-kws"
+            ]
+        },
+        {
+            "name": "build-object_detection",
+            "displayName": "object detection",
+            "configurePreset": "example-user-preset",
+            "jobs": 8,
+            "targets": [
+                "ethos-u-object_detection"
+            ]
+        }
+    ]
+}
+```
+VS Code will include all configurations from both `CMakePresets.json` and `CMakeUserPresets.json` in the drop-down menus in the toolbar.
+Using the *build* option from the VS Code toolbar would both configure the project and build project using the generator that can be set in settings. By default Cmake tools use Ninja generator.
+
+## Using presets from the command line
+
+Presets can be also used from a command-line:
+```commandline
+cmake --preset <config-name>
+cmake --build --preset <config-name>
+```
+where config-name is one of:
+```commandline
+native
+mps3-300-gcc
+mps3-300-clang
+mps3-310-gcc
+mps3-310-clang
+simple-gcc
+simple-clang
+```
+This will automatically configure and build the evaluation-kit into a corresponding folder.
+You can still pass in build flags as usual, for example:
+```commandline
+cmake --preset mps3-300-gcc -DUSE_CASE_BUILD=inference_runner
+cmake --build --preset mps3-300-gcc
+```
\ No newline at end of file