[web] Finished getting started section in devguide.

.editorconfig

@@ -5,7 +5,7 @@ trim_trailing_whitespace = true
 insert_final_newline = true
 indent_size = 4
 
-[*.md]
+[*.{md,pandoc}]
 trim_trailing_whitespace = false
 
 [*.{json,yml,toml}]

web/content/docs/devguide/getting-started/build-configuration.pandoc

@@ -31,7 +31,7 @@ It is preferred to use Conan package manager to install required third-party lib
 Add `-DOGS_USE_CONAN=ON` to the CMake-run (see below).
 
 ::: {.note}
-### Multi-configuration with Conan and Visual Studio
+### <i class="fas fa-exclamation-triangle"></i> Multi-configuration with Conan and Visual Studio
 
 With Conan one build directory corresponds to one configuration. If you want to have e.g. a release and a debug build you need to create two build directories. This is nothing new new to Linux / GCC user but differs to Visual Studios default behavior having just one build-folder / project with different configurations. A typical Visual Studio setup with both Release and Debug configs would be initialized as follows:
 

web/content/docs/devguide/getting-started/prerequisites.pandoc

@@ -168,7 +168,7 @@ $ git lfs install
 :::
 
 ::: {.note}
-### Git LFS installation without admin rights
+### <i class="fas fa-info-circle"></i> Git LFS installation without admin rights
 
 If you do not have rights to install a system package (e.g. on cluster systems) you can [download](https://github.com/git-lfs/git-lfs/releases/latest) a precompiled `git-lfs` executable. Simply put it into your `PATH` and everything should work (remember to run `git lfs install` once!). See also: <https://github.com/git-lfs/git-lfs/wiki/Installation#other>
 :::