From f0d2e66ac03ebc0e994a4be7f644e13657f80689 Mon Sep 17 00:00:00 2001
From: Lars Bilke <lars.bilke@ufz.de>
Date: Wed, 17 Jun 2020 08:56:52 +0200
Subject: [PATCH] Removed link to project file on the web site.
---
web/content/docs/tools/getting-started/first_steps/index.pandoc | 2 +-
web/content/docs/userguide/basics/introduction.pandoc | 2 +-
web/content/docs/userguide/troubleshooting/project-file.pandoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/web/content/docs/tools/getting-started/first_steps/index.pandoc b/web/content/docs/tools/getting-started/first_steps/index.pandoc
index 5a5e545263b..08195fb206a 100644
--- a/web/content/docs/tools/getting-started/first_steps/index.pandoc
+++ b/web/content/docs/tools/getting-started/first_steps/index.pandoc
@@ -13,7 +13,7 @@ weight = 101
This section describes a possible general pre-processing workflow using some of the tools provided by OGS.
-To set up a model domain, [the project file `*.prj`](https://doxygen.opengeosys.org/ogs_file_param__ProjectFile.html) requires additional input files for the mesh and geometry to apply the boundary conditions accordingly.
+To set up a model domain, the project file `*.prj` requires additional input files for the mesh and geometry to apply the boundary conditions accordingly.
The mesh must be provided in VTK's `*.vtu` format, whereas the geometry can be provided either in OGS' internal `*.gml` file format (not to be confused with the Geography Markup Language) or as a `*.vtu` file as well, containing boundary elements only (Multiple `*.vtu` files can be provided in the project file using the `<meshes>` tag). We recommend the usage of the first method for simple 2D meshes with constant boundary conditions, whereas more complicated geometries and conditions might require the latter method. One general advantage in the utilization of `*.vtu` files is that they allow a definition of additional field variables at each mesh node/element in order to implement spatially varying boundary conditions in a similar manner as defining inhomogeneous material properties.
diff --git a/web/content/docs/userguide/basics/introduction.pandoc b/web/content/docs/userguide/basics/introduction.pandoc
index ec5c8c61f65..cd398c7098e 100644
--- a/web/content/docs/userguide/basics/introduction.pandoc
+++ b/web/content/docs/userguide/basics/introduction.pandoc
@@ -27,7 +27,7 @@ Download the latest benchmark files from [GitHub as a .zip-package](https://gith
## Running
-OGS is a command line application and requires the path to a [`.prj`-file](https://doxygen.opengeosys.org/ogs_file_param__ProjectFile.html) as an argument.
+OGS is a command line application and requires the path to a `.prj`-file as an argument.
::: {.win}
To run it open a new command line shell (called *cmd.exe*). Now simply type `ogs` (if the executable is in your `PATH`-environment variable) or specify its full path (e.g.: `C:\Users\MyUserName\Downloads\ogs.exe`) and hit `ENTER`.
diff --git a/web/content/docs/userguide/troubleshooting/project-file.pandoc b/web/content/docs/userguide/troubleshooting/project-file.pandoc
index d0028154ead..69a9587bdd3 100644
--- a/web/content/docs/userguide/troubleshooting/project-file.pandoc
+++ b/web/content/docs/userguide/troubleshooting/project-file.pandoc
@@ -11,7 +11,7 @@ weight = 2
## Check project file syntax with `xmllint`
-[Project files `.prj`](https://doxygen.opengeosys.org/ogs_file_param__ProjectFile.html) have to be valid XML documents. You can check the formatting with the [`xmllint`-tool](http://xmlsoft.org/xmllint.html):
+Project files `.prj` have to be valid XML documents. You can check the formatting with the [`xmllint`-tool](http://xmlsoft.org/xmllint.html):
```bash
xmllint --noout myproj.prj
--
GitLab