ci: provide hugo baseURL via env var

`npm run build` now runs `hugo ... && npm run highlight` instead of just `hugo ...`, so the --baseURL flag was not actually being set. Miraculously this has not yet led to issues in prod, but do it the right way to be safe anyway.

Author: jo3-l

.github/workflows/hugo.yml

@@ -18,7 +18,7 @@ concurrency:
 
 env:
   HUGO_CACHEDIR: /tmp/hugo_cache/
-  HUGO_BASE_URL: 'https://docs-beta.yagpdb.xyz'
+  HUGO_BASEURL: 'https://docs-beta.yagpdb.xyz'
 
 jobs:
   build:
@@ -46,9 +46,7 @@ jobs:
           [[ -f package-lock.json || -f npm-shrinkwrap.json ]] && npm ci || true
 
       - name: Build website
-        # See https://discourse.gohugo.io/t/solved-what-should-be-used-for-the-value-of-site-baseurl/5896
-        # for why we set baseURL here and not in hugo.toml.
-        run: npm run build -- --baseURL=${{ env.HUGO_BASE_URL }}
+        run: npm run build
 
       - name: Setup Pages
         if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/master' }}

README.md

@@ -10,13 +10,11 @@ an experiment to see if it is a viable alternative.
 Install [Node.js](https://nodejs.org/en), clone this repository, install the dependencies with `npm install`, and run
 `npm run dev` to start a local server. The server will automatically rebuild the page when you make changes.
 
-To build the page in release mode, use `npm run build -- --baseURL ...`\*, then serve the generated `public/` directory
+To build the page in release mode, use `HUGO_BASEURL=... npm run build`, then serve the generated `public/` directory
 with your webserver of choice.
 
 For more information, please view our [Contributing Guidelines](.github/CONTRIBUTING.md).
 
-_\*The `--` serves to pass `baseURL` to Hugo as opposed to the `npm run` command._
-
 ### Editor Setup
 
 As this project uses the [EditorConfig](https://editorconfig.org/) standard, you will have to make sure that your