Add deploy preview via surge (#434)

fix #345

- [x] Use a dummy user instead of my personal one (to avoid getting notifications from surge)

- [x] README doc

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/434

.woodpecker/deploy-preview.yaml

@@ -0,0 +1,29 @@
+when:
+  - event: pull_request
+
+steps:
+  build:
+    image: codeberg.org/woodpecker-plugins/node-pm
+    settings:
+      run: build
+      with: npm
+      frozen_lockfile: true
+      ignore_node_modules: true
+
+  deploy-preview:
+    image: docker.io/woodpeckerci/plugin-surge-preview:1.3.1
+    settings:
+      path: '_site/'
+      forge_type: gitea
+      forge_url: https://codeberg.org
+      surge_token:
+        from_secret: surge_token
+      forge_repo_token:
+        from_secret: surge_forge_token
+    failure: ignore
+    when:
+      event: [pull_request, pull_request_closed]
+      path:
+        - content/**
+        - assets/**
+        - .eleventy.js

README.md

@@ -93,6 +93,8 @@ with `package-lock.json` to try to ensure reproducible builds.
 
 It also uses [PageFind](https://pagefind.app/), a static search library.
 
+Deployment previews are generated for every PR using [Surge.sh](https://surge.sh/) through the corresponding [Woodpecker plugin](https://woodpecker-ci.org/plugins/Surge%20preview%20plugin).
+
 ## License and Contributors
 
 This website (excluding bundled fonts) is licensed under CC BY-SA 4.0. See the [LICENSE](LICENSE.md) file for details.