doc: remove reference to Pages site

.github/workflows/pr-to-master.yml

@@ -1,22 +1,22 @@
 name: Test
 
 on:
-   pull_request:
-      branches: [ master ]
+  pull_request:
+    branches: [ master ]
 
 jobs:
-   test:
-      runs-on: ubuntu-latest
+  test:
+    runs-on: ubuntu-latest
 
-      strategy:
-         matrix:
-            node-version: [ 16.x ]
+    strategy:
+      matrix:
+        node-version: [ 16.x ]
 
-      steps:
-         -  uses: actions/checkout@v2
-         -  name: Use Node.js ${{ matrix.node-version }}
-            uses: actions/setup-node@v1
-            with:
-               node-version: ${{ matrix.node-version }}
-         -  run: npm ci
-         -  run: npm test
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm test

.github/workflows/release.yaml

@@ -1,41 +1,41 @@
 name: Build and Deploy
 
 on:
-   push:
-      tags:
-         - 'v[0-9]+.[0-9]+.[0-9]+'
+  push:
+    tags:
+      - 'v[0-9]+.[0-9]+.[0-9]+'
 
-   # Allow running manually from the actions tab
-   workflow_dispatch:
+  # Allow running manually from the actions tab
+  workflow_dispatch:
 
 concurrency:
-   group: "release"
-   cancel-in-progress: true
+  group: "release"
+  cancel-in-progress: true
 
 jobs:
-   build-and-deploy:
-      runs-on: ubuntu-latest
-      steps:
-         -  uses: actions/checkout@master
-            with:
-               lfs: true
+  build-and-deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@master
+        with:
+          lfs: true
 
-         -  name: Build
-            run: |
-               node --version
-               npm --version
-               npm i
-               npm run build
+      - name: Build
+        run: |
+          node --version
+          npm --version
+          npm i
+          npm run build
 
-         -  name: Archive Release
-            run: |
-               pushd dist/plutonium-addon-automation
-               zip -r ../../plutonium-addon-automation.zip .
-               popd
+      - name: Archive Release
+        run: |
+          pushd dist/plutonium-addon-automation
+          zip -r ../../plutonium-addon-automation.zip .
+          popd
 
-         -  name: Upload Release
-            run: |
-               node script/workflows/write-version-notes-file.js ${{github.ref_name}}
-               gh release create "${{github.ref_name}}" --title "${{github.ref_name}}" --notes-file NOTES_FILE.md plutonium-addon-automation.zip dist/plutonium-addon-automation/module.json
-            env:
-               GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: Upload Release
+        run: |
+          node script/workflows/write-version-notes-file.js ${{github.ref_name}}
+          gh release create "${{github.ref_name}}" --title "${{github.ref_name}}" --notes-file NOTES_FILE.md plutonium-addon-automation.zip dist/plutonium-addon-automation/module.json
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.md

@@ -78,7 +78,7 @@ To reference this human-readable macro in the main data files, use `"itemMacro":
 
 ### Bulk conversion from Foundry
 
-In [`docs/`](./docs) (runnable locally with `npm run local-pages`, or available on the web [here](https://thegiddylimit.github.io/plutonium-addon-automation/)) is a simple webpage which you can use to automate some of the data-filling work. On the left, enter a Foundry item's JSON, or load a file at the top. The data will be stripped to just *Plutonium Addon: Automation*-compatible data (plus anything not recognised—sort through that yourself).
+In [`tool/`](./tool) (runnable locally with `npm run local-pages`) is a simple webpage which you can use to automate some of the data-filling work. On the left, enter a Foundry item's JSON, or load a file at the top. The data will be stripped to just *Plutonium Addon: Automation*-compatible data (plus anything not recognised—sort through that yourself).
 
 You can also upload entire `items.db` files, but be aware that the webpage doesn't split the items out by (game-mechanical) datatype, and some modules might be hiding some clutter in that file (e.g. DFCE custom CEs).