adding pictures to fork

docs/5._Controls_Internal/Workflows/writeDocu.md

@@ -4,7 +4,7 @@
 
 [The Grand Unified Theoriy of Documentation](https://docs.divio.com/documentation-system/)
 
-## How to publish Controls Documentation
+## How to publish Controls Docu
 
 Everything is automated. The changes are rendered as soon as you push to the gitea 
 repository [https://gitea.psi.ch/Controls/gitea-pages](https://gitea.psi.ch/Controls/gitea-pages).
@@ -24,6 +24,10 @@ colleagues.
 
 Text
 
+![Fork Button on Gitea page](images/giteaFork_1.png)
+
+Text2
+
 ### Clone your name space version
 
 Text

docs/5._Controls_Internal/Workflows/~writeDocu.md

@@ -1,37 +0,0 @@
-# Writing Controls Documentation
-
-## Different Types of Docu
-
-[The Grand Unified Theoriy of Documentation](https://docs.divio.com/documentation-system/)
-
-## How to publish Controls Docum
-
-Everything is automated. The changes are rendered as soon as you push to the gitea 
-repository [https://gitea.psi.ch/Controls/gitea-pages](https://gitea.psi.ch/Controls/gitea-pages).
-
-The webpage is generated from markdown files using Zensical together with Gitea Actions. 
-The process to setup such page is described here 
-[https://linux.psi.ch/documentation/services/gitea/gitea-pages/](https://linux.psi.ch/documentation/services/gitea/gitea-pages/)
-
-## How to work with your own fork
-
-If several people work at the same time on the same repository  but on different files,
-it can help to create your own fork in your own gitea name space. This will make it 
-easier to debug zensical rendering errors and layout changes without disturbing
-colleagues.
-
-### Fork into your name space
-
-Text
-
-### Clone your name space version
-
-Text
-
-### Review your local changes
-
-Text
-
-### Merge into main Controls Documentation
-
-Text