From 791a5c4c4517a307de42ecb2f110cc39fa4cef47 Mon Sep 17 00:00:00 2001
From: Lars Bilke <lars.bilke@ufz.de>
Date: Mon, 26 Feb 2018 11:28:19 +0100
Subject: [PATCH] [web] Finished getting started section in devguide.
---
.editorconfig | 2 +-
.../docs/devguide/getting-started/build-configuration.pandoc | 2 +-
web/content/docs/devguide/getting-started/prerequisites.pandoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/.editorconfig b/.editorconfig
index dbd6ff49e76..fc48fa2cb6e 100644
--- a/.editorconfig
+++ b/.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}]
diff --git a/web/content/docs/devguide/getting-started/build-configuration.pandoc b/web/content/docs/devguide/getting-started/build-configuration.pandoc
index ce2049a63c6..2be77d4b3ea 100644
--- a/web/content/docs/devguide/getting-started/build-configuration.pandoc
+++ b/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:
diff --git a/web/content/docs/devguide/getting-started/prerequisites.pandoc b/web/content/docs/devguide/getting-started/prerequisites.pandoc
index 86d828f4370..641e3cbaf70 100644
--- a/web/content/docs/devguide/getting-started/prerequisites.pandoc
+++ b/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>
:::
--
GitLab