Added co-author tags

docs/contributors/coauthor-tags.md

@@ -0,0 +1,26 @@
+---
+title: Co-Author tagging
+sidebar_class_name: hidden
+published: false
+---
+
+Don Huan-Huanify
+```
+Co-authored-by: Jannify <[email protected]>
+```
+Tornac
+```
+Co-Authored-By: tornac1234 <[email protected]>
+```
+Clement
+```
+Co-authored-by: dartasen <[email protected]>
+```
+Meas
+```
+Co-authored-by: Measurity <[email protected]>
+```
+Werewolfs
+```
+Co-authored-by: WerewolfsX <[email protected]>
+```

docs/contributors/contribution-guidelines.md

@@ -43,3 +43,7 @@ To prevent issues, and ensure that your code is compatible with the most recent
 merge master into your branch, or rebase your branch on top of master. Even if git(hub) says your code can be merged without conflicts, there might be structural changes (renamings, moved files, refactors, etc), causing the final result to fail compilation, or break at runtime.
 
 It is not desired to remove code just because "it doesn't work", or "causes exceptions in the log". If that's the case, try to fix it (recommended to file the changes in a separate PR), or notify the other Nitrox devs (by creating an issue on github, for example). All code is there for a reason - and someone else spent time creating it.
+
+### Tagging co-authors
+
+If another helped you out to complete a work, it's good sportsmanship to tag them as co-author. [Find yours here](https://github.com/settings/emails) to share them with others. A list of co-author tags can be found [here.](/docs/contributors/coauthor-tags.md)

src/css/custom.css

@@ -53,6 +53,10 @@ h1, .logo__font {
     color: var(--ifm-color-gray-0);
 }
 
+.hidden {
+    display: none !important;
+}
+
 .do {
     color: lawngreen;
 }