Convert Gitlab builder configuration to create Gitlab pages

.gitlab-ci.yml

@@ -2,19 +2,18 @@ variables:
   # We just need to check the current and last commit ATM
   GIT_DEPTH: "2"
 
-stages:
-- build-latex
-
-build-latex:
-  stage: build-latex
+pages:
+  stage: deploy
   tags:
   - latex
   # FIXME: do it sanely when this is resolved: https://gitlab.com/gitlab-org/gitlab-ce/issues/19232
   script:
-  - '{ git diff --quiet --exit-code HEAD^ -- docs/technical_reference_manual/ docs/tex_common/ docs/user_guide && printf "No relevant changes in docs/.\n" >&2 && exit 1; } || make -C docs/ ug trm'
+  - '{ git diff --quiet --exit-code HEAD^ -- VERSION docs/technical_reference_manual/ docs/tex_common/ docs/user_guide && printf "No relevant changes in docs/.\n" >&2 && exit 1; } || mkdir public/ && make -C docs/ ug trm && mv docs/*pdf public/'
   allow_failure: true
   artifacts:
     paths:
-    - docs/fiji_trm.pdf
-    - docs/fiji_user_guide.pdf
+    - public/
     when: on_success
+    expire_in: 1h
+  only:
+  - master

docs/technical_reference_manual/content/03-software.tex

@@ -278,6 +278,6 @@ The unit tests consist of the following phases.
     \item[Instrumentation] The netlists are instrumented with \texttt{fiji\_instrument.pl}.
     \item[Synthesis] The instrumented netlists are quickly checked for syntax errors and the like by synthesizing them with Synplify and filtering out unrelated warnings.
     \item[Simulation] In addition to the syntax check a behavioral simulation tries to find discrepancies between an instrumented and untouched entity of the respective netlist.
-    To that end the test instantiates them in a testbench and compares their output when fed some generated input.
+    To that end, the test instantiates them in a testbench and compares their output when fed some generated input.
     The tests are not exhaustive but very effective since instrumentation bugs usually affect the signal path in a very direct manner.
 \end{description}
\ No newline at end of file

docs/user_guide/content/02-installation.tex

@@ -112,7 +112,7 @@ Finally, you need also to install Verilog-Perl as shown in \Cref{sec:verilog-per
 
 When everything is set up you should be able to launch any FIJI script from a Cygwin shell.
 The GUI applications (e.g., \textit{FIJI Setup}) require a running X server before launch.
-To that end you can start one in the background with
+To that end, you can start one in the background with
 \begin{lstlisting}
 run -p /usr/X11R6/bin XWin -multiwindow -clipboard -silent-dup-error &
 \end{lstlisting}