first stab at mkdocs migration

refactor CSCS and Meg content

add merlin6 quick start

update merlin6 nomachine docs

give the userdoc its own color scheme

we use the Materials default one

refactored slurm general docs merlin6

add merlin6 JB docs

add software support m6 docs

add all files to nav

vibed changes #1

add missing pages

further vibing #2

vibe #3

further fixes

docs/merlin7/02-How-To-Use-Merlin/connect-from-linux.md

@@ -0,0 +1,48 @@
+---
+title: Connecting from a Linux Client
+#tags:
+keywords: linux, connecting, client, configuration, SSH, X11
+last_updated: 07 September 2022
+summary: "This document describes a recommended setup for a Linux client."
+sidebar: merlin7_sidebar
+permalink: /merlin7/connect-from-linux.html
+---
+
+## SSH without X11 Forwarding
+
+This is the standard method. Official X11 support is provided through [NoMachine](nomachine.md).
+For normal SSH sessions, use your SSH client as follows:
+
+```bash
+ssh $username@login001.merlin7.psi.ch
+ssh $username@login002.merlin7.psi.ch
+```
+
+## SSH with X11 Forwarding
+
+Official X11 Forwarding support is through NoMachine. Please follow the document
+[{Job Submission -> Interactive Jobs}](../03-Slurm-General-Documentation/interactive-jobs.md#requirements) and
+[{Accessing Merlin -> NoMachine}](nomachine.md) for more details. However,
+we provide a small recipe for enabling X11 Forwarding in Linux.
+
+* For enabling client X11 forwarding, add the following to the start of ``~/.ssh/config``
+to implicitly add ``-X`` to all ssh connections:
+
+   ```bash
+   ForwardAgent yes
+   ForwardX11Trusted yes
+   ```
+
+* Alternatively, you can add the option ``-Y`` to the ``ssh`` command. In example:
+
+   ```bash
+   ssh -X $username@login001.merlin7.psi.ch
+   ssh -X $username@login002.merlin7.psi.ch
+   ```
+
+* For testing that X11 forwarding works, just run ``sview``. A X11 based slurm view of the cluster should
+popup in your client session:
+
+   ```bash
+   sview
+   ```