diff --git a/external/exchange-channels/duma.md b/external/exchange-channels/duma.md
index 74f459978991af7a6b8304f2b41dae2e092b4beb..e1b44ad2674bd96bf60bf2b466a8a8539af13118 100644
--- a/external/exchange-channels/duma.md
+++ b/external/exchange-channels/duma.md
@@ -70,4 +70,4 @@ Go to the help section of your access link
 
 And follow the steps in the **Using the command line** section.
 
-<br/> ![Alt](../../external/img/duma_cli_tokens.png "Title") <br/><br/><br/>
\ No newline at end of file
+<br/> ![Alt](../../external/img/duma_cli_tokens.png "Title") <br/><br/><br/>
diff --git a/external/exchange-channels/owncloud.md b/external/exchange-channels/owncloud.md
index 2283ef0d9b41e4f47c8936a2d74fed173a55ef61..d55ab010dd608568db813f3239810ee2a2140bc2 100644
--- a/external/exchange-channels/owncloud.md
+++ b/external/exchange-channels/owncloud.md
@@ -33,5 +33,3 @@ When sharing research data, one should observe the following guidance using Ownc
 
 
  **IMPORTANT NOTE: Whenever the LCSB shares an ownCloud folder with you (collaborator), the share password will be reachable via link, which will expire. Therefore you should make a record of your password once you view it.**
-
-
diff --git a/external/img/lums_first-reset-password.png b/external/img/lums_first-reset-password.png
new file mode 100644
index 0000000000000000000000000000000000000000..b05870fec4eee181bdaa2e9030522a3080cfdf36
Binary files /dev/null and b/external/img/lums_first-reset-password.png differ
diff --git a/external/img/lums_home-settings.png b/external/img/lums_home-settings.png
new file mode 100644
index 0000000000000000000000000000000000000000..0c023ff5d389bd9feb7bdf9891e27902b0a7fba1
Binary files /dev/null and b/external/img/lums_home-settings.png differ
diff --git a/external/img/lums_login.png b/external/img/lums_login.png
new file mode 100644
index 0000000000000000000000000000000000000000..b719374ba37ec9f8bd52d650438fa2a0326582fb
Binary files /dev/null and b/external/img/lums_login.png differ
diff --git a/external/img/lums_reset-password.png b/external/img/lums_reset-password.png
new file mode 100644
index 0000000000000000000000000000000000000000..a2797261b753c7fe28adcd8bc6f6abdd1fcdb1b1
Binary files /dev/null and b/external/img/lums_reset-password.png differ
diff --git a/external/img/lums_ticket-main.png b/external/img/lums_ticket-main.png
new file mode 100644
index 0000000000000000000000000000000000000000..af6180e426e8ff14e4ce5d016f8c7130fe7d2d89
Binary files /dev/null and b/external/img/lums_ticket-main.png differ
diff --git a/external/img/lums_ticket-request.png b/external/img/lums_ticket-request.png
new file mode 100644
index 0000000000000000000000000000000000000000..996ef6eedd589f0414149a0815cc4c4c193e6153
Binary files /dev/null and b/external/img/lums_ticket-request.png differ
diff --git a/external/img/r3_logo.png b/external/img/r3_logo.png
new file mode 100644
index 0000000000000000000000000000000000000000..0fb8ea47583f01c6420a4728ee9e1860018f6cff
Binary files /dev/null and b/external/img/r3_logo.png differ
diff --git a/external/lums-passwords/lums-passwords.md b/external/lums-passwords/lums-passwords.md
new file mode 100644
index 0000000000000000000000000000000000000000..1cdbd35f06799244e033ee979e92570803caba45
--- /dev/null
+++ b/external/lums-passwords/lums-passwords.md
@@ -0,0 +1,53 @@
+---
+layout: page
+permalink: /external/lums-passwords/
+---
+
+# LUMS account
+In addition to the standard university account, LCSB researchers and external collaborators are provided with the LUMS (LCSB User Management System) account.
+This serves for internal authentication for resources provided by the LCSB, e.g. LCSB hosted [GitLab](https://git-r3lab.uni.lu), LCSB [OwnCloud](https://owncloud.lcsb.uni.lu) storage or access to virtual machines.
+
+## Requesting LUMS account
+
+  1. Go to [service.uni.lu](https://service.uni.lu).
+
+  2. Login with your university credentials.
+
+  3. Create a ticket requesting a LUMS account:  
+
+     *  Choose **LCSB** ticket service:<br/>
+<img src="/external/img/lums_ticket-main.png" height="300px"><br/>
+
+     *  Navigate to **"BioCore: Application Services"** and choose **"[Request for] a new LUMS account**:<br/>
+    <img src="/external/img/lums_ticket-request.png" height="300px"><br/>
+
+     * If you know already to which services you need access, please specify it in the ticket.
+
+In case you are not a member of the university, please ask your collaborator at the university to request the account for you.
+
+## (Re-)Activating LUMS account upon receiving credentials or after password reset
+
+The password you will receive from the system administrators is temporary and **it will expire after one month**, so you have to reset it as soon as possible. It is usually sent as a link to [PrivateBin](https://howto.lcsb.uni.lu/?passwords). **This link is valid for one week and is deleted after you see it once**, thus you need to keep it open until you have followed these steps to reset your password:
+
+  1. Go to [lums.uni.lu](https://lums.uni.lu) and login with your LUMS username and the temporary password you received.<br>**NOTE:** If you experience any issues at this step, try to use *Chrome* browser for this procedure.<br/><img src="/external/img/lums_login.png" height="200px"><br/>
+  Should the login look different from this, e.g. like a pop-up, click on **x** or **Cancel** to close it.
+
+  2. You will be prompted to reset your password:<br/>
+  <img src="/external/img/lums_first-reset-password.png" height="300px"><br/>
+  3. Enter your temporary password into the field **"Current Password"**.
+  4. Leave the **"OTP"** field blank.
+  5. Enter a new password of your choice in the field **"New Password"** and repeat the same password in the field **"Verify Password"**. This is the actual password you need to use from now on, so make sure to remember it.
+  6. Click on **"Reset Password and Login"**.
+
+It is a good practice to use a password manager which will not only help you to keep track of your passwords so you will never forget it, but it will also help you to generate passwords which are very safe (see [HowTo card](https://howto.lcsb.uni.lu/?passwords) on password management for more detail).
+
+## Changing password for LUMS accounts
+If you want to change your password for the LUMS account, you can:
+  1. Go to [lums.uni.lu](https://lums.uni.lu) and login with your LUMS credentials:
+  <br/><img src="/external/img/lums_login.png" height="200px">
+
+  2. In the top-right corner click on your name and select **Change password**:
+  <br/><img src="/external/img/lums_home-settings.png" height="300px">
+
+  3. Enter your current password and your new password:
+  <br/><img src="/external/img/lums_reset-password.png" height="300px">  
diff --git a/external/markdown/markdown.md b/external/markdown/markdown.md
new file mode 100644
index 0000000000000000000000000000000000000000..770581c73d2a520538dc7209f24b0533f43883be
--- /dev/null
+++ b/external/markdown/markdown.md
@@ -0,0 +1,252 @@
+---
+layout: page
+permalink: /external/markdown/
+---
+
+# Markdown
+Markdown is a lightweight markup language with plain text formatting syntax which became very popular in past decade and which nowadays serves as a standard in various digital communication channels.
+
+## Main features of Markdown:
+  * It has very simple syntax easy to learn.
+    
+  * It is already widely used in scientific community.
+  
+  * It separates content from visual presentation so it allows you to focus on writing, not formatting.
+  
+  * It is a non-proprietary file format.
+  
+  * It is powerful - allows to format text with very little effort.
+
+  * It is portable - since it is actually plain text, it can be opened by literally all text editors.
+  
+  * It is machine readable - as simple text, markdown documents can be tracked and version using a versioning system (Git, SVN)
+  
+  * small file size
+  
+  * easy to convert to other formats - existing editors and command line tools (e.g. [pandoc](https://pandoc.org/) allows for easy conversion between Markdown and other widely used formats like HTML, PDF, docx, LaTeX, etc.
+  
+
+## Syntax
+
+<table>
+  <thead>
+    <tr>
+      <th>Markdown</th>
+      <th>Rendered Output</th>
+    </tr>
+  </thead>
+  <tbody>
+  <tr>
+    <td>
+      <code>
+        # Header 1<br>
+        ## Header 2<br>
+        ### Header 3 <br>
+        #### Header 4 
+      </code>
+    </td>
+    <td>
+      <h1>Header 1</h1><br>
+      <h2>Header 2</h2><br>
+      <h3>Header 3</h3><br>
+      <h4>Header 4</h4>
+    </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+        To **bold** text, add **two asterisks** or __underscores__ before and after a word or phrase.</br>
+        To make text **italic** text, add *one asterisks* or _underscores_.
+        </code>
+      </td>
+      <td>
+        To make phrase <strong>bold</strong> text, add <strong>two asterisks</strong> or <strong>underscores</strong> before and after a word or phrase.</br>
+        To make text <i>italic</i>, add <i>one asterisks</i> or <i>underscores</i>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+        Use numbers for ordered lists:  <br />
+          1. First item<br />
+          2. Second item<br />
+          3. Third item<br />
+          &nbsp;&nbsp;&nbsp;&nbsp;1. Indented item<br />
+          &nbsp;&nbsp;&nbsp;&nbsp;2. Indented item<br />
+          4. Fourth item
+        </code>
+      </td>
+      <td>
+        <ol>
+          <li>First item</li>
+          <li>Second item</li>
+          <li>Third item
+            <ol>
+              <li>Indented item</li>
+              <li>Indented item</li>
+            </ol>
+          </li>
+          <li>Fourth item</li>
+        </ol>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+        For unordered lists
+          * First item<br />
+          * Second item<br />
+          * Third item<br />
+          * Fourth item
+        </code>
+      </td>
+      <td>
+        <ul>
+          <li>First item</li>
+          <li>Second item</li>
+          <li>Third item</li>
+          <li>Fourth item</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+        Include links referring to a web [page](https://www.markdownguide.org/)
+        </code>
+      </td>
+      <td>
+        Include links referring to a web <a href="https://www.markdownguide.org/">page</a>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+        Include local pictures: ![My awesome picture](/img/r3_logo.png)
+        </code>
+      </td>
+      <td>
+        Include local pictures: <img src="../img/img.png">
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+        Include code blocks! </br>
+        ```</br>
+        myAwesomeFunction <- function(x) x+1;</br>
+        # Apply function </br>
+        myAwesomeFunction(2);</br>
+        ```
+        </code>
+      </td>
+      <td>
+      Include code blocks! </br>
+      <code>
+      myAwesomeFunction <- function(x) x+1;</br> 
+      # Apply function</br>  
+      myAwesomeFunction(2);
+      </code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+This is an overview of basic Markdown features. For more in-build features, please see various online [documentation](https://www.markdownguide.org/basic-syntax/).
+
+### Advanced formatting  
+Plain syntax is usually enough. But special requirements lead to development of many of so called ["flavored" markdown syntaxes](https://github.com/commonmark/commonmark-spec/wiki/markdown-flavors) implementing more formatting functionality such as linking different sections, highlighting blocks of code, table extensions, strikethroughs, ...
+
+Another big advantage of Markdown is that it can contain HTML tags, which makes formatting very flexible.
+
+
+## When to use markdown?
+  * **Documentation** - Markdown is a perfect solution for description of a data package, project folder, workflow or code repository. Using Markdown ensures that the description will be accessible to everyone even after decades while still nicely structured. Guide for writing a good README is not covered by this HowTo page but you can find plenty of resources online, e.g.:
+    * [guide](https://data.research.cornell.edu/content/readme) from Cornell University, UK
+    * [GitHub page](https://github.com/mhucka/readmine) for READMEs in a software repository
+    
+  * **Blogging and tutorials** - structured document with chunks of code, pictures and results of the analyses can be easily converted to HTML format and posted on personal/team websites.
+  
+  * **Notes and meeting minutes** - you can use following template for simple and nicely structured meeting notes:
+<table>
+  <thead>
+    <tr>
+      <th>Markdown</th>
+      <th>Rendered Output</th>
+    </tr>
+  </thead>
+  <tbody>
+  <tr>
+    <td>
+      <code>
+    # DocTitle</br>
+    ### Attendees:</br>
+    ### Location:</br>
+    ## Objective / Agenda</br>
+    ## Meeting Notes</br>
+      * first note </br>
+      * second note </br>
+      * ...</br>
+      </br>
+    ## Actions</br>
+    - [ ] Josh, Alice and Cindy will do this.</br>
+    - [x] Bob stops doing that.</br>
+    - [ ] Will and Tom will take care of those
+    </code>
+    </td>
+    <td>
+      <code>
+    <h1>DocTitle</h1></br>
+    <h3> Attendees:<h3></br>
+    <h3> Location:</h3></br>
+    <h2> Objective / Agenda</h2></br>
+    <h2> Meeting Notes</h2></br>
+      <ul>
+        <li> first note</li>
+        <li>second note</li>
+        <li>...</li>
+      </ul>
+    <h2> Actions</h2></br>
+    <input type="checkbox" > Josh, Alice and Cindy will do this.</input></br>
+    <input type="checkbox" checked="checked"> Bob stops doing that.</input></br>
+    <input type="checkbox" > Vanessa and Tom will take care of those</input></br>
+    </code>
+    </td>
+  </tr>
+</tbody>
+</table>
+
+  * **Analyses,reports and papers** - embedding [R markdown](https://rmarkdown.rstudio.com/) in an R project allows you to include executable code and related text in the very same document. This brings unprecedented level of consistency, shareability and reproducibility into the workflows.
+ 
+  * **Online discussion forums** - many scientific and non-scientific discussion forums and social networks support Markdown for formatting the content of messages (e.g. [StackOverflow](https://stackoverflow.com/editing-help), [GitHub](https://help.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax), Reddit or even Facebook) 
+  
+  * **Presentations** - variety of tools support Markdown-powered slide generation, e.g. [reveal.js](https://revealjs.com/#/), [HackerSlides](https://github.com/jacksingleton/hacker-slides) or [landslide](https://github.com/adamzap/landslide)
+ 
+## Cases when Markdown is not easily applicable
+
+  * **Official documents** like legal agreements and project proposals could be in theory written in Markdown but it is not yet accepted by administrative processes.
+  
+  * **Big structured tables** with multilevel headers or special formatting can be written in HTML editors and then pasted into your Markdown document.
+  
+  * **Thesis writing** requires support of citation managers and additional formatting. This can be achieved but usually is conditioned by embedding Latex into your workflow.
+
+## Editors
+Markdown file can be written in any text editor. There are many editors supporting rendering and live preview, here are some of them: 
+
+  * Freeware
+    * Atom 
+    * Dillinger
+    * Visual Studio Code
+    * ghostwriter
+    * Typora 
+    * HackMD
+    * ...
+    
+  * Payware:
+    * iA Writer
+    * SublimeText
+    * ByWord
+    
+  * Online
+    * [GitHub pages](https://pages.github.com/)
+    * [stackedit.io](stackedit.io)
diff --git a/index.md b/index.md
index 4714610d03558140077f986169211a8ecd9958d2..9e417eaba5b05fe3c01dbcd71366adc446f4f7ad 100644
--- a/index.md
+++ b/index.md
@@ -12,3 +12,5 @@ Bioinformatics Core assists Luxembourg Centre for Systems Biomedicine ([LCSB](ht
 
   * [Exchange data with collaborators](./external/exchange-channels/)
   * [Registering human-subject data to DAISY](./external/daisy/)
+  * [Markdown markup language](./external/markdown/)
+  * [LUMS account](./external/lums-passwords)