From 060de4ab45fdcbb3c86eb1d572465cd839948065 Mon Sep 17 00:00:00 2001
From: Andre_601 <11576465+Andre601@users.noreply.github.com>
Date: Fri, 23 Oct 2026 01:27:11 +0200
Subject: [PATCH 1/2] Add git-pages section

---
 docs/user-guide/deploying-your-docs.md | 46 ++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/docs/user-guide/deploying-your-docs.md b/docs/user-guide/deploying-your-docs.md
index 7202b8fd..9865dd2f 100644
--- a/docs/user-guide/deploying-your-docs.md
+++ b/docs/user-guide/deploying-your-docs.md
@@ -119,6 +119,52 @@ You need to add `pip install properdocs` to the `.readthedocs.yaml` file's
 [rtd]: https://readthedocs.org/
 [instructions]: https://docs.readthedocs.com/platform/stable/intro/mkdocs.html
 
+## git-pages
+
+[git-pages] is a self-hostable alternative to solutions such as GitHub Pages. It is
+generally compatible with any git-forge (GitHub, GitLab, Forgejo, etc.) and different
+public instances are available to use, such as [Codeberg Pages].
+
+For example, a simple Forgejo Actions Workflow to deploy your Site to Codeberg Pages
+might look something like this:
+
+```yaml
+name: Deploy Site
+
+on:
+  push:
+
+jobs:
+  deploy:
+    runs-on: codeberg-tiny
+    steps:
+      - uses: https://code.forgejo.org/actions/checkout@v7
+      - uses: https://code.forgejo.org/actions/setup-python@v7
+        with:
+          python-version: 3.7
+      - run: |
+          pip install properdocs properdocs-theme-mkdocs
+          properdocs build
+      - uses: https://code.forgejo.org/actions/git-pages@v2
+        with:
+          site: https://example.codeberg.page
+          source: site/
+```
+
+### Custom Domains
+
+git-pages uses a different aproach to Custom Domains compared to GitHub Pages. What
+method is used depends on the instance's configuration and how you deploy your site:
+
+- Deploying through a webhook requires a `TXT` Record with `_git-pages-repository`
+(optionally with subdomain) and your Git Repository URL from where you deploy as value.
+- Deploying through git-pages' Forgejo Action requires a `TXT` Record with
+`git-pages-forge-allowlist` (optionally with subdomain) and your Git Repository URL
+from where you deploy as value.
+
+[git-pages]: https://git-pages.org/
+[Codeberg Pages]: https://codeberg.page
+
 ## Other Providers
 
 Any hosting provider which can serve static files can be used to serve

From 68bbd4976ab1e6abcc4e8bda5b0a11b351c84e5c Mon Sep 17 00:00:00 2001
From: Andre_601 <11576465+Andre601@users.noreply.github.com>
Date: Fri, 23 Oct 2026 01:36:27 +0200
Subject: [PATCH 2/2] Fix linting and grammar issues

---
 docs/user-guide/deploying-your-docs.md | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/docs/user-guide/deploying-your-docs.md b/docs/user-guide/deploying-your-docs.md
index 9865dd2f..62fa435b 100644
--- a/docs/user-guide/deploying-your-docs.md
+++ b/docs/user-guide/deploying-your-docs.md
@@ -153,14 +153,15 @@ jobs:
 
 ### Custom Domains
 
-git-pages uses a different aproach to Custom Domains compared to GitHub Pages. What
+git-pages uses a different approach to Custom Domains compared to GitHub Pages. What
 method is used depends on the instance's configuration and how you deploy your site:
 
-- Deploying through a webhook requires a `TXT` Record with `_git-pages-repository`
-(optionally with subdomain) and your Git Repository URL from where you deploy as value.
-- Deploying through git-pages' Forgejo Action requires a `TXT` Record with
-`git-pages-forge-allowlist` (optionally with subdomain) and your Git Repository URL
-from where you deploy as value.
+-   Deploying through a webhook requires a `TXT` Record with `_git-pages-repository`
+    (optionally with subdomain) and your Git Repository URL from where you deploy as
+    value.
+-   Deploying through git-pages' Forgejo Action requires a `TXT` Record with `git-pages-forge-allowlist`
+    (optionally with subdomain) and your Git Repository URL from where you deploy as
+    value.
 
 [git-pages]: https://git-pages.org/
 [Codeberg Pages]: https://codeberg.page