From c8891942357438e0100ab7dca0ada30cd12bdf5b Mon Sep 17 00:00:00 2001 From: Artyom Bologov Date: Wed, 22 Jul 2026 01:45:58 +0400 Subject: [PATCH] pages: Use example.org in all git-pages examples --- content/codeberg-pages/troubleshooting.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/codeberg-pages/troubleshooting.md b/content/codeberg-pages/troubleshooting.md index d36c268..15da850 100644 --- a/content/codeberg-pages/troubleshooting.md +++ b/content/codeberg-pages/troubleshooting.md @@ -41,7 +41,7 @@ Say, we add this (broken) [redirect rule](/codeberg-pages/advanced-usage/#redire /*/ /:splat.html 301 ``` -After committing it and opening a page like `https://website.tld/hello`, we are redirected to a 404 page. +After committing it and opening a page like `https://example.org/hello`, we are redirected to a 404 page. Something must be brokein in redirects. However, we don’t know that for sure. Need to check. @@ -50,9 +50,9 @@ There are two ways to find out what’s broken in the website: ``` # Plain web request -curl https://website.tld/.git-pages/manifest.json +curl https://example.org/.git-pages/manifest.json # Or a dedicated tool from git-pages -git-pages-cli --debug-manifest https://website.tld +git-pages-cli --debug-manifest https://example.org ``` In either case, you get huge JSONs with meta-information about the website.