docs: Add script for generating PDFs from markdown, add usage info

pcsx2/Docs/!How_To_Update_Docs.txt

@@ -1,19 +0,0 @@
-== How To Update PCSX2 Docs == 
-
-Source Directory: ./pcsx2/pcsx2/Docs 
-Release Directory: /pcsx2/bin/Docs 
-
-Docs should be written in the source directory first in an easily editable
-format. Currently, Markdown is the preferred format due to its simple markup and
-easy portability. GitHub's built-in preview functions are a huge benefit as 
-well.
-
-Visual Studio Code is a cross platform text editor/development platform that can
-handle Markdown syntax, plus extensions are available to enable in-editor
-previewing and PDF generation. However, this is not a requirement since other
-editors will support Markdown, and worst case GitHub supports editing Markdown
-files in-browser.
-
-Once docs are finished, convert them from Markdown to PDFs using the tool of
-your choice. Move the PDFs to the above Release Directory. 
-

pcsx2/Docs/.gitignore

@@ -0,0 +1 @@
+*.pdf

pcsx2/Docs/README.md

@@ -0,0 +1,50 @@
+# Documentation Artifacts
+
+- Source Directory: `/pcsx2/pcsx2/Docs`
+- Release Directory: `/pcsx2/bin/Docs`
+
+Docs should be written in the source directory first in an easily editable format. Currently, Markdown is the preferred format due to its simple markup and easy portability. GitHub's built-in preview functions are a huge benefit as well.
+
+Visual Studio Code is a cross platform text editor/development platform that can handle Markdown syntax, plus extensions are available to enable in-editor previewing and PDF generation. However, this is not a requirement since other editors will support Markdown, and worst case GitHub supports editing Markdown files in-browser.
+
+## How to Generate
+
+### Setup
+
+To generate the documentation artifacts into the release directory, you will require the following:
+
+- `pandoc`
+  - Converts from Markdown to PDF
+- `miktex` or something similar that provides `pdflatex`
+  - this is what generates the PDF file
+
+#### Linux / MacOS
+
+Consult pandoc's official documentation - https://pandoc.org/installing.html
+
+#### Windows
+
+In a PowerShell shell, run the following:
+
+```ps1
+> iwr -useb get.scoop.sh | iex
+> scoop install pandoc latex
+```
+
+If you prefer Chocolatey or using the installer, consult pandoc's official documentation - https://pandoc.org/installing.html
+
+### Usage
+
+Run the following, this assumes you have access to bash, either by virtue of running on linux or through something like `git-bash` on Windows.
+
+```bash
+> ./gen-docs.sh
+```
+
+> You can override the default output directory like so - `OUT_DIR=<PATH> ./gen-docs.sh`
+
+### Customizing Output
+
+For generating the PDF's this popular template is used and has many features that could be useful https://github.com/Wandmalfarbe/pandoc-latex-template#usage reference it's documentation to take advantage of those if desired.
+
+TODO commit with +x `git update-index --chmod=+x .\gen-docs.sh`

pcsx2/Docs/gen-docs.sh

@@ -0,0 +1,19 @@
+#!/bin/bash
+
+OUT_DIR=${OUT_DIR:-"../../bin/docs"}
+
+## Generate and Move Markdown->PDFs
+### Configuration Guide
+
+pushd Configuration_Guide
+pandoc --template "../eisvogel.tex" --toc "Configuration_Guide.md" -o "Configuration_Guide.pdf"
+popd
+mv -f "./Configuration_Guide/Configuration_Guide.pdf" "$OUT_DIR"
+
+### The rest!
+
+find . -maxdepth 1 -name "*.md" -not -path "./README.md"  | while read filename; do
+  filename="${filename%.*}"
+  pandoc --template "./eisvogel.tex" --toc "$filename.md" -o "$filename.pdf"
+  mv -f "$filename.pdf" "$OUT_DIR"
+done