feat(docs): add fork-preview banner, dual Atom feeds, gh-pages reset

.github/workflows/docs-build-check.yml

@@ -0,0 +1,33 @@
+name: Docs Build Check
+
+on:
+  pull_request:
+  push:
+    branches:
+      - master
+      - admincom/docs-improvements
+
+permissions:
+  contents: read
+
+jobs:
+  build-check:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+          python-version: "3.11"
+
+      - name: Install dependencies
+        run: uv sync --locked
+
+      - name: Build docs (strict)
+        run: uv run mkdocs build --strict

.github/workflows/docs-deploy.yml

@@ -0,0 +1,54 @@
+name: Deploy Docs Preview
+
+on:
+  push:
+    branches:
+      - master
+      - admincom/docs-improvements
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+concurrency:
+  group: docs-deploy
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+          python-version: "3.11"
+
+      - name: Install dependencies
+        run: uv sync --locked
+
+      - name: Configure git identity for the gh-deploy commit
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+
+      # This fork's preview serves at a dedicated dev domain, docs-dev.peeringdb.dk,
+      # distinct from upstream production's docs.peeringdb.com. The domain is set
+      # as a repo variable (Settings -> Secrets and variables -> Actions ->
+      # Variables -> SITE_URL_OVERRIDE) rather than hardcoded here, so it can be
+      # changed without editing this file. It feeds both scripts/generate_cname.py
+      # (writes docs/CNAME) and scripts/generate_blog_atom_feed.py (the feed's
+      # self-link), so both stay in sync with wherever this deploy actually serves
+      # from. Safe by default if this branch is ever merged upstream: with no
+      # variable set there, both hooks fall back to mkdocs.yml's site_url
+      # (docs.peeringdb.com), so no manual CNAME edit is needed at merge time.
+      - name: Deploy to gh-pages
+        env:
+          SITE_URL_OVERRIDE: ${{ vars.SITE_URL_OVERRIDE }}
+        run: uv run mkdocs gh-deploy --clean --force --no-history

.gitignore

@@ -2,3 +2,8 @@ site/
 .DS_Store
 venv/
 .venv/
+docs/blog/atom.xml
+docs/release_notes/atom.xml
+docs/CNAME
+__pycache__/
+*.pyc

README.md

@@ -11,7 +11,7 @@ To work on and change these documents, you'll need git, python, and pip.
 
 - CentOS
     ```sh
-    sudo yum install python-pip
+    sudo dnf install python3 python3-pip
     ```
 
 Fork the repo

docs/blog/mfa_mandatory.md

@@ -1,7 +1,7 @@
 # PeeringDB Will Require MFA and API Keys to Log In
 *March 13, 2025*
 
-You must have a [second factor](/howto/enable_require_2fa/) to log in to PeeringDB starting on 1 July 2025. If you automate updates using [our API](/api_specs/), you'll need to use an [API Key](/howto/api_keys/).
+You must have a [second factor](/howto/authenticate/#multi-factor-authentication-mfa) to log in to PeeringDB starting on 1 July 2025. If you automate updates using [our API](/api_specs/), you'll need to use an [API Key](/howto/api_keys/).
 
 But anonymous usage will not be going away. You can query the website or API without authenticating. This change will impact users who make updates or need access to contact information published in PeeringDB.
 

docs/blog/peeringdb_2022_user_survey.md

@@ -11,7 +11,7 @@ We had about 250 responses to last year’s survey which helped guide our produc
 * Added FIDO U2F 2FA support to [www.peeringdb.com](https://www.peeringdb.com/)
 * Normalized place names
 
-We’ve also published more documents in our [HOWTO documentation series](/howto/). 
+We’ve also published more documents in our [HOWTO documentation series](/howtos/). 
 
 Steve McManus, PeeringDB Product Committee Chair, says: "*The 2021 survey helped us focus development where it was most needed. We used it to develop our roadmap. We are still implementing things we have learned from previous surveys but want your input on how we should adapt. Please take a few moments of their time to help us make PeeringDB a better service!*”
 

docs/blogs.md

@@ -2,6 +2,8 @@
 
 PeeringDB blogs provide deeper insight into the releases and product roadmap.
 
+Subscribe via [Atom feed](blog/atom.xml) to get notified of new posts.
+
 ## 2026
 - [Do We Still Need Public Beta?](blog/public_beta.md) - July 26, 2026
 - [Data Quality for Networks](blog/data_quality_for_networks.md) - July 1, 2026