[web] Added some screen recordings for clone, config, build and tests.

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

@@ -80,6 +80,8 @@ CMake tries to autodetect your compiler so in most cases this should be enough:
 $ cmake ../ogs
 ```
 
+{{< asciinema url="https://asciinema.org/a/249004" >}}
+
 ::: {.note}
 #### <i class="far fa-check"></i> Pro Tip: Use the Visual Studio command line
 

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

@@ -43,6 +43,8 @@ To speedup the compilation process append the number of cores of your cpu to the
 $ make -j 8
 ```
 
+{{< asciinema url="https://asciinema.org/a/249005" >}}
+
 ### Option: Eclipse
 
 To let CMake generate the Eclipse project files change the generator argument to the CMake run:

web/content/docs/devguide/getting-started/get-the-source-code.pandoc

@@ -32,17 +32,16 @@ $ git config remote.pushdefault origin
 $ git config push.default current
 ```
 
-**Note:** We use `git lfs clone` instead of the regular `git clone` to significantly speed up the cloning of the repo and its test data files. See [this for more information](https://github.com/ufz/ogs/pull/1978).
-
 This creates a new folder `ogs` in your current working directory with the OGS source code. After this step, the remote called `origin` refers to your fork on GitHub. It also sets the default remote for pushes to be `origin` and the default push behavior to `current`. Together this means that if you just type `git push`, the current branch is pushed to the `origin` remote (git version >= 2.5 required).
 
 Create a second remote called `upstream` that points at the main OGS repository and fetch from it:
 
 ```bash
 $ git remote add upstream https://github.com/ufz/ogs
-$ git [lfs] fetch upstream # The lfs-equivalent of the fetch command is more efficient
+$ git fetch upstream
 ```
 
+{{< asciinema url="https://asciinema.org/a/249002" speed="3" rows="20" >}}
 
 ## Optional: Working on a new feature
 

web/content/docs/devguide/testing/unit-testing.pandoc

@@ -17,6 +17,8 @@ weight = 1021
 
 Googletest is already included in the OGS source code. Running tests is as simple as building the `tests`-target.
 
+{{< asciinema url="https://asciinema.org/a/249006" >}}
+
 ## Writing Tests
 
 All tests are located inside the *Tests*-directory in library-specific subfolders. To write a new test you simply create a new *.cpp*-file and use the googletest macros.