fix broken links

external/access/lums-passwords/lums-passwords.md

@@ -31,7 +31,7 @@ In case you are not a member of the university, please ask your collaborator at
 
 ## (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:
+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]({{ '/?access:passwords' | relative_url }}). **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="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.
@@ -43,7 +43,7 @@ The password you will receive from the system administrators is temporary and **
   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).
+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]({{ '/?access:passwords' | relative_url }}) on password management for more detail).
 
 ## Changing password for LUMS accounts
 If you want to change your password for the LUMS account, you can:

external/contribute/web-ide/web-ide.md

@@ -13,7 +13,10 @@ This shows how to use Gitlab Web IDE to add or edit a howto-card:
 
 Before you start, please make sure that you have the correct access rights to edit the repository.
 
-*Note: If you do not have the rights to edit the repository, you can either ask for permissions by contacting the repository maintainers, or use your own copy of the repository (called a `fork`). Please follow [these instructions](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork) to obtain your copy (fork). You can then [mirror the fork automatically](/cards/contribute:mirror-fork) to keep in sync.*
+*Note: If you do not have the rights to edit the repository, you can either ask for permissions by contacting
+the repository maintainers, or use your own copy of the repository (called a `fork`).
+Please follow [these instructions](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork) to
+obtain your copy (fork). You can then [mirror the fork automatically]({{ '/?contribute:mirror-fork' | relative_url }}) to keep in sync.*
 
 A clear difference between editing a file in a git-tracked repository compared to a live document is that you can make an edit directly, and then suggesting the change. You can make this edit on your own version (called a `branch`), and then request to merge your changes into the main repository (through opening a `merge request`).
 

external/integrity/spreadsheets/spreadsheets.md

@@ -42,7 +42,7 @@ For reproducibility purposes, the collected data should be always exported from
 
 ### Table
 
-- Keep header column names machine readable. You can follow the same best practices as for file naming (see our [Card on file naming](../naming/file_naming.md)).
+- Keep header column names machine readable. You can follow the same best practices as for file naming (see our [Card on file naming](https://howto.lcsb.uni.lu/?integrity:naming)).
 - Keep values in columns atomic.
 - Use primary keys - values in one particular column should be unique for the whole table. This will allow you to create unique references pointing to one and only one observation/record.
 - Do not insert empty rows or columns which would split the table in two.