Update ChibiOS-Contrib.

2026-09-08 11:34:00 +02:00 · 2025-10-27 15:28:54 +11:00
483 changed files with 1101 additions and 13671 deletions
@@ -25,7 +25,7 @@ jobs:
    if: github.repository == 'qmk/qmk_firmware'

    steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        fetch-depth: 1
        persist-credentials: false
@@ -4,7 +4,7 @@ permissions: {}

 on:
  schedule:
-    - cron: "*/30 * * * *"
+    - cron: "*/5 * * * *"

 jobs:
  automatic_approve:
@@ -28,7 +28,7 @@ jobs:
    if: github.repository == 'qmk/qmk_firmware'

    steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        fetch-depth: 0

@@ -1,289 +0,0 @@
-name: Bootstrap Script Testing
-
-on:
-  push:
-    branches: [master, develop, xap]
-    paths:
-    - 'util/env-bootstrap.sh'
-    - '.github/workflows/bootstrap_testing.yml'
-  pull_request:
-    paths:
-    - 'util/env-bootstrap.sh'
-    - '.github/workflows/bootstrap_testing.yml'
-  workflow_dispatch:
-
-permissions:
-  contents: read
-
-jobs:
-  prep:
-    runs-on: ubuntu-latest
-
-    outputs:
-      any_changed: ${{ steps.file_changes.outputs.any_changed }}
-
-    steps:
-    - name: Get changed files
-      id: file_changes
-      if: ${{ github.event_name == 'pull_request' }}
-      uses: tj-actions/changed-files@v47
-      with:
-        use_rest_api: true
-        files: |
-          util/env-bootstrap.sh
-          .github/workflows/bootstrap_testing.yml
-
-  bootstrap-test-linux:
-    name: Bootstrap (Linux)
-
-    needs: prep
-    if: ${{ github.event_name != 'pull_request' || needs.prep.outputs.any_changed == 'true' }}
-
-    runs-on: ubuntu-latest
-
-    strategy:
-      fail-fast: false
-      matrix:
-        distribution:
-          # Ubuntu/Debian based
-          - debian:11
-          - debian:12
-          - debian:13
-          - ubuntu:20.04
-          - ubuntu:22.04
-          - ubuntu:24.04
-
-          # RHEL/CentOS/Fedora based
-          - fedora:41
-          - fedora:42
-          - fedora:43
-          - rockylinux:8
-          - rockylinux:9
-          - rockylinux/rockylinux:10
-          - almalinux:8
-          - almalinux:9
-          - almalinux:10
-
-          # OpenSUSE based (we skip Tumbleweed as it has issues with package versions between pattern installs and other dependencies preinstalled into the base container)
-          - opensuse/leap:latest
-
-          # Gentoo-based
-          - gentoo/stage3:latest
-
-          # Arch based
-          - archlinux:latest
-          - cachyos/cachyos:latest
-          - manjarolinux/base:latest
-
-    container:
-      image: ${{ matrix.distribution }}
-      options: --privileged
-
-    steps:
-      - name: Install base dependencies
-        run: |
-          # Attempt to run the package installation up to 10 times to mitigate transient network issues
-          for n in $(seq 1 10); do
-            {
-              echo "Attempt #$n of 10 to install base dependencies:"
-              case "${{ matrix.distribution }}" in
-                *ubuntu*|*debian*)
-                  apt-get update
-                  apt-get install -y sudo git passwd
-                  ;;
-                *fedora*|*rockylinux*|*almalinux*)
-                  dnf install -y sudo git passwd findutils  # findutils=xargs
-                  ;;
-                *suse*)
-                  zypper --non-interactive refresh
-                  zypper --non-interactive install sudo git shadow findutils  # findutils=xargs
-                  ;;
-                *gentoo*)
-                  emerge-webrsync
-                  emerge --noreplace --ask=n sudo dev-vcs/git shadow findutils  # findutils=xargs
-                  ;;
-                *archlinux*|*cachyos*|*manjaro*)
-                  pacman -Syu --noconfirm
-                  pacman -S --noconfirm sudo git
-                  ;;
-              esac
-            } && break || sleep 10
-          done
-
-          # Fix PAM configuration for sudo in containers
-          # Fix /etc/shadow permissions - common issue in container environments
-          chmod 640 /etc/shadow || chmod 400 /etc/shadow || true
-
-          # Disable problematic PAM modules that commonly fail in RHEL-like containers
-          sed -i 's/^session.*pam_systemd.so/#&/' /etc/pam.d/sudo || true
-          sed -i 's/^session.*pam_loginuid.so/#&/' /etc/pam.d/sudo || true
-
-          # Ensure proper sudoers configuration
-          echo 'Defaults !requiretty' >> /etc/sudoers
-          echo 'Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"' >> /etc/sudoers
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 1
-          submodules: recursive
-          path: qmk_firmware
-
-      - name: Create test user
-        run: |
-          # Create a test user for the bootstrap script
-          useradd -m -s /bin/bash -U testuser
-          echo 'testuser:testpassword' | chpasswd || true
-          
-          # Configure passwordless sudo
-          echo "root ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers  # some distros complain about root not being in sudoers
-          echo "testuser ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers
-          
-          # Test sudo functionality
-          sudo -u testuser whoami || echo "Sudo test failed, but continuing..."
-
-      - name: Move QMK repository to test user home
-        run: |
-          # Add upstream remote to the cloned repository so `qmk doctor` doesn't flag a warning
-          git -C qmk_firmware remote add upstream https://github.com/qmk/qmk_firmware.git
-          # Move the QMK repository to the test user's home directory
-          mv qmk_firmware /home/testuser/qmk_firmware
-          chown -R testuser:testuser /home/testuser/qmk_firmware
-
-      - name: Run bootstrap script
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          # Ensure the bootstrap script can access sudo
-          sudo -u testuser --preserve-env=GITHUB_TOKEN bash -c "
-            export CONFIRM=1
-            export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-            cd /home/testuser
-            bash /home/testuser/qmk_firmware/util/env-bootstrap.sh
-          "
-
-      - name: Install dependencies
-        run: |
-          sudo -u testuser bash -c "
-            /home/testuser/.local/share/uv/tools/qmk/bin/python -m pip install -r /home/testuser/qmk_firmware/requirements.txt
-          "
-
-      - name: Test QMK CLI
-        run: |
-          sudo -u testuser bash -c "
-            export PATH=/home/testuser/.local/bin:\$PATH
-            cd /home/testuser
-            qmk setup -y -H /home/testuser/qmk_firmware  # setup implies doctor, no need to run it separately
-            cd /home/testuser/qmk_firmware
-            qmk mass-compile -j $(nproc) -e DUMP_CI_METADATA=yes -f 'keyboard_name==*onekey*' -km reset -p || touch .failed  # Compile a bunch of different platforms
-          "
-          
-          cd /home/testuser/qmk_firmware
-          ./util/ci/generate_failure_markdown.sh > $GITHUB_STEP_SUMMARY || true
-          [ ! -e .failed ] || exit 1
-
-  bootstrap-test-macos:
-    name: Bootstrap (macOS)
-
-    needs: prep
-    if: ${{ github.event_name != 'pull_request' || needs.prep.outputs.any_changed == 'true' }}
-
-    strategy:
-      fail-fast: false
-      matrix:
-        os:
-          - macos-14        # Apple Silicon ARM64
-          - macos-15        # Apple Silicon ARM64
-          - macos-15-intel  # Intel x64
-          - macos-26        # Apple Silicon ARM64
-
-    runs-on: ${{ matrix.os }}
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 1
-          submodules: recursive
-
-      - name: Run bootstrap script
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          # Add upstream remote to the cloned repository so `qmk doctor` doesn't flag a warning
-          git remote add upstream https://github.com/qmk/qmk_firmware.git
-          # Run the bootstrap script
-          export CONFIRM=1
-          sh ./util/env-bootstrap.sh
-
-      - name: Install dependencies
-        run: |
-          $HOME/.local/share/uv/tools/qmk/bin/python -m pip install -r requirements.txt
-
-      - name: Test QMK CLI
-        run: |
-          # Add QMK CLI to PATH (bootstrap script installs it to ~/.local/bin on macOS)
-          export PATH="$HOME/.local/bin:$PATH"
-          qmk setup -y -H .  # setup implies doctor, no need to run it separately
-          qmk mass-compile -j $(sysctl -n hw.ncpu) -e DUMP_CI_METADATA=yes -f 'keyboard_name==*onekey*' -km reset || touch .failed  # Compile a bunch of different platforms
-          
-          ./util/ci/generate_failure_markdown.sh > $GITHUB_STEP_SUMMARY || true
-          [ ! -e .failed ] || exit 1
-
-  bootstrap-test-windows:
-    name: Bootstrap (Windows)
-
-    needs: prep
-    if: ${{ github.event_name != 'pull_request' || needs.prep.outputs.any_changed == 'true' }}
-
-    strategy:
-      fail-fast: false
-      matrix:
-        msys-variant:
-          - mingw64
-          - clang64
-          - ucrt64
-
-    runs-on: windows-latest
-    defaults:
-      run:
-        shell: msys2 {0}
-
-    steps:
-      - name: Install MSYS2
-        uses: msys2/setup-msys2@v2
-        with:
-          msystem: ${{ matrix.msys-variant }}
-          pacboy: >-
-            git:
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 1
-          submodules: recursive
-
-      - name: Run bootstrap script
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          # Add upstream remote to the cloned repository so `qmk doctor` doesn't flag a warning
-          git remote add upstream https://github.com/qmk/qmk_firmware.git
-          # Run the bootstrap script
-          export CONFIRM=1
-          sh ./util/env-bootstrap.sh
-
-      - name: Install dependencies
-        run: |
-          /opt/uv/tools/qmk/Scripts/python -m pip install -r requirements.txt
-
-      - name: Test QMK CLI
-        run: |
-          # Add QMK CLI to PATH (bootstrap script installs it to /opt/uv/tools/bin on Windows MSYS2)
-          export PATH="/opt/uv/tools/bin:$PATH"
-          qmk setup -y -H .  # setup implies doctor, no need to run it separately
-          qmk mass-compile -j $(nproc) -e DUMP_CI_METADATA=yes -f 'keyboard_name==*onekey*' -km reset || touch .failed  # Compile a bunch of different platforms
-          
-          ./util/ci/generate_failure_markdown.sh > $GITHUB_STEP_SUMMARY || true
-          [ ! -e .failed ] || exit 1
-
@@ -35,15 +35,17 @@ jobs:
      slice_length: ${{ steps.generate_slice_length.outputs.slice_length }}

    steps:
+      - name: Install prerequisites
+        run: |
+          apt-get update
+          apt-get install -y jq
+
      - name: Disable safe.directory check
        run: |
          git config --global --add safe.directory '*'

      - name: Checkout QMK Firmware
-        uses: actions/checkout@v6
-
-      - name: Install dependencies
-        run: pip3 install -r requirements-dev.txt
+        uses: actions/checkout@v5

      - name: Determine concurrency
        id: generate_slice_length
@@ -80,12 +82,12 @@ jobs:
          git config --global --add safe.directory '*'

      - name: Checkout QMK Firmware
-        uses: actions/checkout@v6
+        uses: actions/checkout@v5
        with:
          fetch-depth: 0

      - name: Download firmwares
-        uses: actions/download-artifact@v7
+        uses: actions/download-artifact@v5
        with:
          pattern: firmware-*
          path: .
@@ -27,15 +27,17 @@ jobs:
      targets: ${{ steps.generate_targets.outputs.targets }}

    steps:
+      - name: Install prerequisites
+        run: |
+          apt-get update
+          apt-get install -y jq
+
      - name: Disable safe.directory check
        run: |
          git config --global --add safe.directory '*'

      - name: Checkout QMK Firmware
-        uses: actions/checkout@v6
-
-      - name: Install dependencies
-        run: pip3 install -r requirements-dev.txt
+        uses: actions/checkout@v5

      - name: Generate build targets
        id: generate_targets
@@ -60,7 +62,7 @@ jobs:
          echo "targets=$(jq -c 'keys' targets.json)" >> $GITHUB_OUTPUT

      - name: Upload targets json
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v4
        with:
          name: targets-${{ inputs.keymap }}
          path: targets.json
@@ -77,18 +79,20 @@ jobs:
        target: ${{ fromJson(needs.generate_targets.outputs.targets) }}

    steps:
+      - name: Install prerequisites
+        run: |
+          apt-get update
+          apt-get install -y jq
+
      - name: Disable safe.directory check
        run: |
          git config --global --add safe.directory '*'

      - name: Checkout QMK Firmware
-        uses: actions/checkout@v6
-
-      - name: Install dependencies
-        run: pip3 install -r requirements-dev.txt
+        uses: actions/checkout@v5

      - name: Get target definitions
-        uses: actions/download-artifact@v7
+        uses: actions/download-artifact@v5
        with:
          name: targets-${{ inputs.keymap }}
          path: .
@@ -105,15 +109,10 @@ jobs:
        continue-on-error: true
        run: |
          export NCPUS=$(( $(nproc 2>/dev/null || sysctl -n hw.ncpu 2>/dev/null || getconf _NPROCESSORS_ONLN 2>/dev/null) -1 ))
-          targets=$(jq -r '.["${{ matrix.target }}"].targets' targets.json | tr ' ' '\n' | sort)
-          if [ -z "${targets}" ]; then
-            echo "Zero build targets detected"
-            exit 0
-          fi
-          qmk mass-compile -t -j $NCPUS -e DUMP_CI_METADATA=yes $targets || touch .failed
+          qmk mass-compile -t -j $NCPUS -e DUMP_CI_METADATA=yes $(jq -r '.["${{ matrix.target }}"].targets' targets.json) || touch .failed

      - name: Upload binaries
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v4
        with:
          name: firmware-${{ inputs.keymap }}-${{ matrix.target }}
          if-no-files-found: ignore
@@ -137,17 +136,17 @@ jobs:

    steps:
      - name: Checkout QMK Firmware
-        uses: actions/checkout@v6
+        uses: actions/checkout@v5

      - name: Download firmwares
-        uses: actions/download-artifact@v7
+        uses: actions/download-artifact@v5
        with:
          pattern: firmware-${{ inputs.keymap }}-*
          path: .
          merge-multiple: true

      - name: Upload all firmwares
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v4
        with:
          name: firmware-${{ inputs.keymap }}
          if-no-files-found: ignore
@@ -24,12 +24,11 @@ jobs:
    - name: Disable safe.directory check
      run : git config --global --add safe.directory '*'

-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        submodules: recursive

    - name: Install dependencies
      run: pip3 install -r requirements-dev.txt
-
    - name: Run tests
      run: qmk pytest
@@ -1,34 +0,0 @@
-name: Generate Develop Docs
-
-permissions:
-  contents: write
-
-on:
-  push:
-    branches:
-    - develop
-    paths:
-    - 'builddefs/docsgen/**'
-    - 'tmk_core/**'
-    - 'quantum/**'
-    - 'platforms/**'
-    - 'docs/**'
-    - '.github/workflows/docs.yml'
-
-jobs:
-  generate:
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Deploy Develop
-      if: ${{ github.repository == 'qmk/qmk_firmware' }}
-      uses: actions/github-script@v8
-      with:
-        github-token: ${{ secrets.QMK_BOT_TOKEN }}
-        script: |
-          const result = await github.rest.actions.createWorkflowDispatch({
-            owner: 'qmk',
-            repo: 'qmk_docs_devel',
-            workflow_id: 'develop.yml',
-            ref: 'main',
-          })
@@ -15,7 +15,7 @@ jobs:
    if: github.repository == 'qmk/qmk_firmware'

    steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        token: ${{ secrets.QMK_BOT_TOKEN }}
        fetch-depth: 0
@@ -30,15 +30,14 @@ jobs:
    container: ghcr.io/qmk/qmk_cli

    steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        fetch-depth: 1

    - name: Install dependencies
-      run: pip3 install -r requirements-dev.txt
-
-    - name: Install nvm
      run: |
+        apt-get update && apt-get install -y rsync doxygen
+        # install nvm
        touch $HOME/.bashrc
        wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash

@@ -57,7 +56,7 @@ jobs:

    - name: Deploy
      if: ${{ github.event_name == 'push' && github.repository == 'qmk/qmk_firmware' }}
-      uses: JamesIves/github-pages-deploy-action@v4.7.6
+      uses: JamesIves/github-pages-deploy-action@v4.7.3
      with:
          token: ${{ secrets.GITHUB_TOKEN }}
          branch: gh-pages
@@ -21,7 +21,7 @@ jobs:
        - riot

    steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        token: ${{ secrets.QMK_BOT_TOKEN }}
        fetch-depth: 0
@@ -26,7 +26,7 @@ jobs:
    - name: Disable safe.directory check
      run : git config --global --add safe.directory '*'

-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        fetch-depth: 0

@@ -19,7 +19,7 @@ jobs:
    - name: Disable safe.directory check
      run : git config --global --add safe.directory '*'

-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        fetch-depth: 0

@@ -47,7 +47,7 @@ jobs:
        git config user.email 'hello@qmk.fm'

    - name: Create Pull Request
-      uses: peter-evans/create-pull-request@v8
+      uses: peter-evans/create-pull-request@v7
      if: ${{ github.repository == 'qmk/qmk_firmware'}}
      with:
        token: ${{ secrets.QMK_BOT_TOKEN }}
@@ -18,7 +18,7 @@ jobs:
    - name: Disable safe.directory check
      run : git config --global --add safe.directory '*'

-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        fetch-depth: 0

@@ -19,10 +19,7 @@ jobs:
    - name: Disable safe.directory check
      run : git config --global --add safe.directory '*'

-    - uses: actions/checkout@v6
-
-    - name: Install dependencies
-      run: pip3 install -r requirements-dev.txt
+    - uses: actions/checkout@v5

    - name: Run qmk generators
      run: |
@@ -19,10 +19,7 @@ jobs:
    - name: Disable safe.directory check
      run : git config --global --add safe.directory '*'

-    - uses: actions/checkout@v6
-
-    - name: Install dependencies
-      run: pip3 install -r requirements-dev.txt
+    - uses: actions/checkout@v5

    - name: Run qmk generators
      run: |
@@ -37,7 +34,7 @@ jobs:
        git config user.email 'hello@qmk.fm'

    - name: Create Pull Request
-      uses: peter-evans/create-pull-request@v8
+      uses: peter-evans/create-pull-request@v7
      if: ${{ github.repository == 'qmk/qmk_firmware'}}
      with:
        token: ${{ secrets.QMK_BOT_TOKEN }}
@@ -26,12 +26,10 @@ jobs:
    container: ghcr.io/qmk/qmk_cli

    steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v5
      with:
        submodules: recursive
-
    - name: Install dependencies
      run: pip3 install -r requirements-dev.txt
-
    - name: Run tests
      run: qmk test-c
@@ -65,8 +65,6 @@ cmake-build-debug
 CMakeLists.txt
 *.pdf
 *.zip
-.env
-.envrc

 # Let these ones be user specific, since we have so many different configurations
 *.code-workspace
@@ -97,11 +95,6 @@ tags
 *.mpeg
 *.ttf
 *.otf
-# Un-ignore limited image file formats in docs
-!docs/public/**.gif
-!docs/public/**.jpg
-!docs/public/**.jpeg
-!docs/public/**.png

 # Things Travis sees
 /.vs
@@ -19,18 +19,18 @@ endif
 ifneq ($(QMK_USERSPACE),)
    ifneq ("$(wildcard $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_5)/keymap.json)","")
        KEYMAP_JSON := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_5)/keymap.json
-        KEYMAP_JSON_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_5)
+        KEYMAP_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_5)
    else ifneq ("$(wildcard $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_4)/keymap.json)","")
        KEYMAP_JSON := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_4)/keymap.json
-        KEYMAP_JSON_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_4)
+        KEYMAP_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_4)
    else ifneq ("$(wildcard $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_3)/keymap.json)","")
        KEYMAP_JSON := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_3)/keymap.json
-        KEYMAP_JSON_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_3)
+        KEYMAP_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_3)
    else ifneq ("$(wildcard $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_2)/keymap.json)","")
        KEYMAP_JSON := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_2)/keymap.json
-        KEYMAP_JSON_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_2)
+        KEYMAP_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_2)
    else ifneq ("$(wildcard $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_1)/keymap.json)","")
        KEYMAP_JSON := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_1)/keymap.json
-        KEYMAP_JSON_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_1)
+        KEYMAP_PATH := $(QMK_USERSPACE)/$(MAIN_KEYMAP_PATH_1)
    endif
 endif
@@ -255,8 +255,6 @@ endif
 COMMUNITY_RULES_MK = $(shell $(QMK_BIN) generate-community-modules-rules-mk -kb $(KEYBOARD) --quiet --escape --output $(INTERMEDIATE_OUTPUT)/src/community_rules.mk $(KEYMAP_JSON))
 include $(COMMUNITY_RULES_MK)

-ifneq ($(COMMUNITY_MODULES),)
-
 $(INTERMEDIATE_OUTPUT)/src/community_modules.h: $(KEYMAP_JSON) $(DD_CONFIG_FILES)
 	@$(SILENT) || printf "$(MSG_GENERATING) $@" | $(AWK_CMD)
 	$(eval CMD=$(QMK_BIN) generate-community-modules-h -kb $(KEYBOARD) --quiet --output $(INTERMEDIATE_OUTPUT)/src/community_modules.h $(KEYMAP_JSON))
@@ -291,8 +289,6 @@ SRC += $(INTERMEDIATE_OUTPUT)/src/community_modules.c

 generated-files: $(INTERMEDIATE_OUTPUT)/src/community_modules.h $(INTERMEDIATE_OUTPUT)/src/community_modules.c $(INTERMEDIATE_OUTPUT)/src/community_modules_introspection.c $(INTERMEDIATE_OUTPUT)/src/community_modules_introspection.h $(INTERMEDIATE_OUTPUT)/src/led_matrix_community_modules.inc $(INTERMEDIATE_OUTPUT)/src/rgb_matrix_community_modules.inc

-endif
-
 include $(BUILDDEFS_PATH)/converters.mk

 # Generate the board's version.h file.
@@ -474,10 +470,8 @@ ifneq ($(wildcard $(QMK_USERSPACE)),)
 endif

 # If the equivalent users directory exists in userspace, use that in preference to anything currently in the main repo
-ifneq ($(QMK_USERSPACE),)
-	ifneq ($(wildcard $(QMK_USERSPACE)/$(USER_PATH)),)
-    	USER_PATH := $(QMK_USERSPACE)/$(USER_PATH)
-	endif
+ifneq ($(wildcard $(QMK_USERSPACE)/$(USER_PATH)),)
+    USER_PATH := $(QMK_USERSPACE)/$(USER_PATH)
 endif

 # Pull in user level rules.mk
@@ -10,10 +10,10 @@ define SEARCH_LAYOUTS_REPO
    LAYOUT_KEYMAP_JSON := $$(LAYOUT_KEYMAP_PATH)/keymap.json
    LAYOUT_KEYMAP_C := $$(LAYOUT_KEYMAP_PATH)/keymap.c
    ifneq ("$$(wildcard $$(LAYOUT_KEYMAP_JSON))","")
+        -include $$(LAYOUT_KEYMAP_PATH)/rules.mk
        KEYMAP_JSON := $$(LAYOUT_KEYMAP_JSON)
-        KEYMAP_JSON_PATH := $$(LAYOUT_KEYMAP_PATH)
-    endif
-    ifneq ("$$(wildcard $$(LAYOUT_KEYMAP_C))","")
+        KEYMAP_PATH := $$(LAYOUT_KEYMAP_PATH)
+    else ifneq ("$$(wildcard $$(LAYOUT_KEYMAP_C))","")
        -include $$(LAYOUT_KEYMAP_PATH)/rules.mk
        KEYMAP_C := $$(LAYOUT_KEYMAP_C)
        KEYMAP_PATH := $$(LAYOUT_KEYMAP_PATH)
@@ -125,7 +125,7 @@ ifeq ($(strip $(MOUSEKEY_ENABLE)), yes)
    MOUSE_ENABLE := yes
 endif

-VALID_POINTING_DEVICE_DRIVER_TYPES := adns5050 adns9800 analog_joystick azoteq_iqs5xx cirque_pinnacle_i2c cirque_pinnacle_spi paw3204 paw3222 pmw3320 pmw3360 pmw3389 pimoroni_trackball custom
+VALID_POINTING_DEVICE_DRIVER_TYPES := adns5050 adns9800 analog_joystick azoteq_iqs5xx cirque_pinnacle_i2c cirque_pinnacle_spi paw3204 pmw3320 pmw3360 pmw3389 pimoroni_trackball custom
 ifeq ($(strip $(POINTING_DEVICE_ENABLE)), yes)
    ifeq ($(filter $(POINTING_DEVICE_DRIVER),$(VALID_POINTING_DEVICE_DRIVER_TYPES)),)
        $(call CATASTROPHIC_ERROR,Invalid POINTING_DEVICE_DRIVER,POINTING_DEVICE_DRIVER="$(POINTING_DEVICE_DRIVER)" is not a valid pointing device type)
@@ -157,8 +157,6 @@ ifeq ($(strip $(POINTING_DEVICE_ENABLE)), yes)
            SRC += drivers/sensors/cirque_pinnacle.c
            SRC += drivers/sensors/cirque_pinnacle_gestures.c
            SRC += $(QUANTUM_DIR)/pointing_device/pointing_device_gestures.c
-        else ifeq ($(strip $(POINTING_DEVICE_DRIVER)), paw3222)
-            SPI_DRIVER_REQUIRED = yes
        else ifeq ($(strip $(POINTING_DEVICE_DRIVER)), pimoroni_trackball)
            I2C_DRIVER_REQUIRED = yes
        else ifneq ($(filter $(strip $(POINTING_DEVICE_DRIVER)),pmw3360 pmw3389),)
@@ -224,7 +224,6 @@
    "PERMISSIVE_HOLD_PER_KEY": {"info_key": "tapping.permissive_hold_per_key", "value_type": "flag"},
    "RETRO_TAPPING": {"info_key": "tapping.retro", "value_type": "flag"},
    "RETRO_TAPPING_PER_KEY": {"info_key": "tapping.retro_per_key", "value_type": "flag"},
-    "SPECULATIVE_HOLD": {"info_key": "tapping.speculative_hold", "value_type": "flag"},
    "TAP_CODE_DELAY": {"info_key": "qmk.tap_keycode_delay", "value_type": "int"},
    "TAP_HOLD_CAPS_DELAY": {"info_key": "qmk.tap_capslock_delay", "value_type": "int"},
    "TAPPING_TERM": {"info_key": "tapping.term", "value_type": "int"},
@@ -1,190 +0,0 @@
-# QMK Breaking Changes - 2025 Nov 30 Changelog
-
-## Notable Features {#notable-features}
-
-### Speculative Hold option for mod-taps: hold mods instantly while unsettled [#25572](https://github.com/qmk/qmk_firmware/pull/25572)
-
-Speculative Hold makes mod-tap keys more responsive by applying the modifier instantly on keydown, before the tap-hold decision is made. This is especially useful for actions like Shift+click and Ctrl+scroll wheel with an external mouse, which can feel laggy with standard mod-taps.
-
-The firmware holds the modifier speculatively. Once the key's behavior is settled:
-
-* If held, the modifier remains active as expected until the key is released.
-* If tapped, the speculative modifier is canceled just before the tapping keycode is sent.
-
-Speculative Hold applies the modifier early but does not change the underlying tap-hold decision logic. Speculative Hold is compatible to use in combination with any other tap-hold options.
-
-see the [Speculative Hold](../tap_hold#speculative-hold) documentation for more information.
-
-## Changes Requiring User Action
-
-### Updated Keyboard Codebases
-
-| Old Keyboard Name                | New Keyboard Name       |
-|----------------------------------|-------------------------|
-| 0xcb/splaytoraid/32u4            | 0xcb/splaytoraid        |
-| 0xcb/splaytoraid/rp2040_ce       | 0xcb/splaytoraid        |
-| 1upkeyboards/sweet16v2/kb2040    | 1upkeyboards/sweet16v2  |
-| 1upkeyboards/sweet16v2/pro_micro | 1upkeyboards/sweet16v2  |
-| 40percentclub/gherkin/kb2040     | 40percentclub/gherkin   |
-| 40percentclub/gherkin/pro_micro  | 40percentclub/gherkin   |
-| durgod/dgk6x/venus               | durgod/dgk6x/venus_ansi |
-
-### Reduce tap dance memory usage, move state out of data [#25415](https://github.com/qmk/qmk_firmware/pull/25415)
-
-The tap dance state has been separated from the action structure. Custom tap dance functions now receive the state as a separate parameter instead of accessing it through `action->state`.
-
-If your keymap uses custom tap dance functions that access the tap dance state, you need to update your code.
-
-* You can't use `action->state`. Instead you need to call `tap_dance_state_t *tap_dance_get_state(uint8_t tap_dance_idx)` to get the state.
-* You now get a pointer to the state, so use `->` notation rather than `.` notation to get fields from it.
-
-### Before:
-```c
-bool process_record_user(uint16_t keycode, keyrecord_t *record) {
-    tap_dance_action_t *action;
-
-    switch (keycode) {
-        case TD(CT_CLN):
-            action = tap_dance_get(QK_TAP_DANCE_GET_INDEX(keycode));
-            if (!record->event.pressed && action->state.count && !action->state.finished) {
-                tap_dance_tap_hold_t *tap_hold = (tap_dance_tap_hold_t *)action->user_data;
-                tap_code16(tap_hold->tap);
-            }
-
-    }
-    return true;
-}
-```
-### After:
-```c
-bool process_record_user(uint16_t keycode, keyrecord_t *record) {
-    tap_dance_action_t *action;
-    tap_dance_state_t* state;
-    switch (keycode) {
-        case TD(CT_CLN):
-            action = tap_dance_get(QK_TAP_DANCE_GET_INDEX(keycode));
-            state = tap_dance_get_state(QK_TAP_DANCE_GET_INDEX(keycode));
-            if (!record->event.pressed && state != NULL && state->count && !state->finished) {
-                tap_dance_tap_hold_t *tap_hold = (tap_dance_tap_hold_t *)action->user_data;
-                tap_code16(tap_hold->tap);
-            }
-    }
-    return true;
-}
-```
-
-## Deprecation Notices
-
-In line with the [notice period](../support_deprecation_policy#how-much-advance-notice-will-be-given), deprecation notices for larger items are listed here.
-
-### Remove override of QK_{LED,RGB}_MATRIX_TOGGLE keycode [#25672](https://github.com/qmk/qmk_firmware/pull/25672)
-
-[#24649](https://github.com/qmk/qmk_firmware/pull/24649) implemented genetic behavior, including keycodes, to cycle flags.
-
-Any overriding of existing keycodes that duplicate this behavior will be removed to ensure consistency with core functionality.
-
-## Full changelist
-
-Core:
-* suspend: suppress wake up keypress ([#23389](https://github.com/qmk/qmk_firmware/pull/23389))
-* [Feature Improvement]add option to keep layer state when recording dynamic macros ([#24418](https://github.com/qmk/qmk_firmware/pull/24418))
-* Add generic handling to cycle LED/RGB Matrix flags ([#24649](https://github.com/qmk/qmk_firmware/pull/24649))
-* Implement `mod_t` packed struct ([#25168](https://github.com/qmk/qmk_firmware/pull/25168))
-* Implement minimal connection update logic ([#25334](https://github.com/qmk/qmk_firmware/pull/25334))
-* Reduce tap dance memory usage, move state out of data ([#25415](https://github.com/qmk/qmk_firmware/pull/25415))
-* Refactor debounce algorithm with static allocation ([#25515](https://github.com/qmk/qmk_firmware/pull/25515))
-* Restructure Pixel Rain interval code ([#25516](https://github.com/qmk/qmk_firmware/pull/25516))
-* Guard remapping logic with MAGIC_ENABLE ([#25537](https://github.com/qmk/qmk_firmware/pull/25537))
-* Update default OLED font ([#25565](https://github.com/qmk/qmk_firmware/pull/25565))
-* Speculative Hold option for mod-taps: hold mods instantly while unsettled. ([#25572](https://github.com/qmk/qmk_firmware/pull/25572))
-* Simplify hue calculation in raindrops animation ([#25587](https://github.com/qmk/qmk_firmware/pull/25587))
-* Simplify tap_code16_delay ([#25595](https://github.com/qmk/qmk_firmware/pull/25595))
-* Debounce: Deprecate num_rows parameter ([#25632](https://github.com/qmk/qmk_firmware/pull/25632))
-* Add I2C Transmit and Receive function ([#25637](https://github.com/qmk/qmk_firmware/pull/25637))
-* [QP] Minor cleanup and support for RGB888 surface ([#25706](https://github.com/qmk/qmk_firmware/pull/25706))
-* Restrict mouse timer activation to movement keycodes ([#25716](https://github.com/qmk/qmk_firmware/pull/25716))
-* Update STM32F446 default HSE to 8MHz ([#25717](https://github.com/qmk/qmk_firmware/pull/25717))
-* making flowtap timer public so it can be used easily with combos ([#25731](https://github.com/qmk/qmk_firmware/pull/25731))
-* Add PixArt PAW-3222 mouse sensor driver ([#25763](https://github.com/qmk/qmk_firmware/pull/25763))
-* Merge upstream uf2conv changes ([#25786](https://github.com/qmk/qmk_firmware/pull/25786))
-* Partially skip generating community modules when none enabled ([#25819](https://github.com/qmk/qmk_firmware/pull/25819))
-
-CLI:
-* Generate default encoder resolution for sparse config ([#25247](https://github.com/qmk/qmk_firmware/pull/25247))
-* Add DIP Switch map support to keymap.json ([#25431](https://github.com/qmk/qmk_firmware/pull/25431))
-* Add return code to `qmk userspace-doctor` ([#25775](https://github.com/qmk/qmk_firmware/pull/25775))
-* Better defaulting of `{RGB,LED}_MATRIX_DEFAULT_FLAGS` ([#25785](https://github.com/qmk/qmk_firmware/pull/25785))
-* add BCD versions of QMK Version ([#25804](https://github.com/qmk/qmk_firmware/pull/25804))
-* Lint error on missing keyboard readme ([#25814](https://github.com/qmk/qmk_firmware/pull/25814))
-
-Submodule updates:
-* Update ChibiOS-Contrib. ([#25751](https://github.com/qmk/qmk_firmware/pull/25751))
-
-Keyboards:
-* `atreus`: restore intended matrix implementations ([#24082](https://github.com/qmk/qmk_firmware/pull/24082))
-* add SteelSeries prime, a stripped down prime+ ([#24719](https://github.com/qmk/qmk_firmware/pull/24719))
-* Add new macropad Sharkropad ([#24961](https://github.com/qmk/qmk_firmware/pull/24961))
-* Addition of the D60B tsangan pcb ([#25245](https://github.com/qmk/qmk_firmware/pull/25245))
-* Migrate `eeconfig_init_kb` implementations to config ([#25422](https://github.com/qmk/qmk_firmware/pull/25422))
-* Generate `CUSTOM_MATRIX = lite` without `matrix_pins.custom` ([#25453](https://github.com/qmk/qmk_firmware/pull/25453))
-* Add classic48 keyboard ([#25492](https://github.com/qmk/qmk_firmware/pull/25492))
-* add durgod venus iso support ([#25526](https://github.com/qmk/qmk_firmware/pull/25526))
-* Migrate `g_led_config` to DD (0-9, A) ([#25558](https://github.com/qmk/qmk_firmware/pull/25558))
-* Migrate `g_led_config` to DD (B, C) ([#25559](https://github.com/qmk/qmk_firmware/pull/25559))
-* Migrate `g_led_config` to DD (D) ([#25560](https://github.com/qmk/qmk_firmware/pull/25560))
-* Migrate `g_led_config` to DD (E, F) ([#25561](https://github.com/qmk/qmk_firmware/pull/25561))
-* Remove duplication of RP2040 config defaults ([#25563](https://github.com/qmk/qmk_firmware/pull/25563))
-* Refactor 40percentclub/ut47 ([#25571](https://github.com/qmk/qmk_firmware/pull/25571))
-* E7-V2 Implementation ([#25594](https://github.com/qmk/qmk_firmware/pull/25594))
-* Migrate `g_led_config` to DD (G) ([#25598](https://github.com/qmk/qmk_firmware/pull/25598))
-* Migrate `g_led_config` to DD (H) ([#25599](https://github.com/qmk/qmk_firmware/pull/25599))
-* Migrate `g_led_config` to DD (I) ([#25600](https://github.com/qmk/qmk_firmware/pull/25600))
-* Migrate `g_led_config` to DD (JK1) ([#25601](https://github.com/qmk/qmk_firmware/pull/25601))
-* Migrate `g_led_config` to DD (K2) ([#25602](https://github.com/qmk/qmk_firmware/pull/25602))
-* Migrate `g_led_config` to DD (K3) ([#25603](https://github.com/qmk/qmk_firmware/pull/25603))
-* Migrate `g_led_config` to DD (K4) ([#25605](https://github.com/qmk/qmk_firmware/pull/25605))
-* Migrate `g_led_config` to DD (K5) ([#25606](https://github.com/qmk/qmk_firmware/pull/25606))
-* Migrate `g_led_config` to DD (K6) ([#25607](https://github.com/qmk/qmk_firmware/pull/25607))
-* Refactor `40percentclub/gherkin` ([#25608](https://github.com/qmk/qmk_firmware/pull/25608))
-* Refactor `0xcb/splaytoraid` ([#25609](https://github.com/qmk/qmk_firmware/pull/25609))
-* Refactor `1upkeyboards/sweet16v2` ([#25610](https://github.com/qmk/qmk_firmware/pull/25610))
-* Migrate `g_led_config` to DD (K7) ([#25616](https://github.com/qmk/qmk_firmware/pull/25616))
-* Migrate `g_led_config` to DD (L) ([#25617](https://github.com/qmk/qmk_firmware/pull/25617))
-* Migrate `g_led_config` to DD (M1) ([#25618](https://github.com/qmk/qmk_firmware/pull/25618))
-* Migrate `g_led_config` to DD (M2) ([#25619](https://github.com/qmk/qmk_firmware/pull/25619))
-* Migrate `g_led_config` to DD (M3) ([#25620](https://github.com/qmk/qmk_firmware/pull/25620))
-* Migrate `g_led_config` to DD (NO) ([#25621](https://github.com/qmk/qmk_firmware/pull/25621))
-* Migrate `g_led_config` to DD (P) ([#25622](https://github.com/qmk/qmk_firmware/pull/25622))
-* Migrate `g_led_config` to DD (QR) ([#25623](https://github.com/qmk/qmk_firmware/pull/25623))
-* Migrate `g_led_config` to DD (S) ([#25624](https://github.com/qmk/qmk_firmware/pull/25624))
-* Migrate `g_led_config` to DD (TUW) ([#25625](https://github.com/qmk/qmk_firmware/pull/25625))
-* Remove idobao *_DISABLE_UNDERGLOW behaviour ([#25638](https://github.com/qmk/qmk_firmware/pull/25638))
-* Migrate `g_led_config` to DD (YZ) ([#25650](https://github.com/qmk/qmk_firmware/pull/25650))
-* Tidy Keebio keyboards ([#25653](https://github.com/qmk/qmk_firmware/pull/25653))
-* Remove encoder resolution where duplicating defaults ([#25654](https://github.com/qmk/qmk_firmware/pull/25654))
-* Custom oled fonts cleanup ([#25665](https://github.com/qmk/qmk_firmware/pull/25665))
-* Binepad KnobX1 - refactor `x1_layer_led` function as weak ([#25668](https://github.com/qmk/qmk_firmware/pull/25668))
-* Add DD {LED,RGB}_MATRIX_DEFAULT_FLAGS support ([#25671](https://github.com/qmk/qmk_firmware/pull/25671))
-* keyboards: Add Royal Kludge RK61 ([#25694](https://github.com/qmk/qmk_firmware/pull/25694))
-* Add TRKeyboard TRK2 keyboard ([#25754](https://github.com/qmk/qmk_firmware/pull/25754))
-
-Keyboard fixes:
-* Fixup `kprepublic/bm60hsrgb/rev2` ([#25644](https://github.com/qmk/qmk_firmware/pull/25644))
-* Fixup `kprepublic/bm60hsrgb_iso/rev2` ([#25648](https://github.com/qmk/qmk_firmware/pull/25648))
-* Fixup `kprepublic/bm60hsrgb_poker/rev2` ([#25649](https://github.com/qmk/qmk_firmware/pull/25649))
-* Fixup `rgbkb/pan` ([#25678](https://github.com/qmk/qmk_firmware/pull/25678))
-* Align use of keymap level `_kb` callbacks ([#25774](https://github.com/qmk/qmk_firmware/pull/25774))
-
-Others:
-* Rework converter docs ([#18314](https://github.com/qmk/qmk_firmware/pull/18314))
-* Update USBaspLoader ISP instructions ([#25590](https://github.com/qmk/qmk_firmware/pull/25590))
-* Add LED/RGB Matrix flags API docs ([#25673](https://github.com/qmk/qmk_firmware/pull/25673))
-
-Bugs:
-* Fix single key combos activating only once ([#25198](https://github.com/qmk/qmk_firmware/pull/25198))
-* Fix RGB matrix not syncing and turning off properly on timeout ([#25467](https://github.com/qmk/qmk_firmware/pull/25467))
-* Fix drv haptics docs by using the correct function name ([#25733](https://github.com/qmk/qmk_firmware/pull/25733))
-* Fix Magic GUI masking logic ([#25780](https://github.com/qmk/qmk_firmware/pull/25780))
-* Fix Speculative Hold to enable also right-handed RSFT, RCTL by default. ([#25797](https://github.com/qmk/qmk_firmware/pull/25797))
-* Fix community layout keymap discovery ([#25802](https://github.com/qmk/qmk_firmware/pull/25802))
-* Fix preference of output file for 'qmk generate-autocorrect-data' ([#25818](https://github.com/qmk/qmk_firmware/pull/25818))
@@ -0,0 +1,3 @@
+# Refactor debounce algorithm with static allocation [#25515](https://github.com/qmk/qmk_firmware/pull/25515)
+
+Removed dynamic memory allocation (malloc, free) from all debounce implementations for improved efficiency on embedded systems and to avoid runtime allocation overhead. Refactored state arrays to use direct indexing, simplifying code and eliminating pointer arithmetic. Standardized usage of MATRIX_ROWS_PER_HAND throughout the codebase to ensure consistent support for split keyboards.
@@ -0,0 +1,4 @@
+# Changes Requiring User Action
+## Debounce: Deprecate init and remove num_rows parameter [#25632](https://github.com/qmk/qmk_firmware/pull/25632)
+
+With dynamic memory allocation removed from all debounce implementations ([#25515](https://github.com/qmk/qmk_firmware/pull/25515)), the `num_rows` parameter has been removed from the `debounce_init()` and `debounce()` functions. The `MATRIX_ROWS_PER_HAND` is now used by default in every implementation.
@@ -214,7 +214,7 @@
                    { "text": "My Pull Request Was Flagged", "link": "/breaking_changes_instructions" },
                    {
                        "text": "Most Recent ChangeLog",
-                        "link": "/ChangeLog/20251130"
+                        "link": "/ChangeLog/20250831"
                    },
                    { "text": "Past Breaking Changes", "link": "/breaking_changes_history" },
                    { "text": "Deprecation Policy", "link": "/support_deprecation_policy" }
@@ -10,25 +10,25 @@ Practically, this means QMK merges the `develop` branch into the `master` branch

 ## What has been included in past Breaking Changes?

-* [2025 Nov 30](ChangeLog/20251130)
 * [2025 Aug 31](ChangeLog/20250831)
 * [2025 May 25](ChangeLog/20250525)
+* [2025 Feb 23](ChangeLog/20250223)
 * [Older Breaking Changes](breaking_changes_history)

 ## When is the next Breaking Change?

-The next Breaking Change is scheduled for February 22, 2026.
+The next Breaking Change is scheduled for November 30, 2025.

 ### Important Dates

-* 2025 Nov 30 - `develop` is tagged with a new release version. Each push to `master` is subsequently merged to `develop` by GitHub actions.
-* 2026 Jan 25 - `develop` closed to new PRs.
-* 2026 Jan 25 - Call for testers.
-* 2026 Feb 8 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes
-* 2026 Feb 15 - `develop` is locked, only critical bugfix PRs merged.
-* 2026 Feb 20 - `master` is locked, no PRs merged.
-* 2026 Feb 22 - Merge `develop` to `master`.
-* 2026 Feb 22 - `master` is unlocked. PRs can be merged again.
+* 2025 Aug 31 - `develop` is tagged with a new release version. Each push to `master` is subsequently merged to `develop` by GitHub actions.
+* 2025 Nov 2 - `develop` closed to new PRs.
+* 2025 Nov 2 - Call for testers.
+* 2025 Nov 16 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes
+* 2025 Nov 23 - `develop` is locked, only critical bugfix PRs merged.
+* 2025 Nov 28 - `master` is locked, no PRs merged.
+* 2025 Nov 30 - Merge `develop` to `master`.
+* 2025 Nov 30 - `master` is unlocked. PRs can be merged again.

 ## What changes will be included?

@@ -2,7 +2,6 @@

 This page links to all previous changelogs from the QMK Breaking Changes process.

-* [2025 Nov 30](ChangeLog/20251130) - version 0.31.0
 * [2025 Aug 31](ChangeLog/20250831) - version 0.30.0
 * [2025 May 25](ChangeLog/20250525) - version 0.29.0
 * [2025 Feb 23](ChangeLog/20250223) - version 0.28.0
@@ -4,7 +4,7 @@ QMK presents itself to the host as a regular HID keyboard device, and as such re

 There are two notable exceptions: the Caterina bootloader, usually seen on Pro Micros, and the HalfKay bootloader shipped with PJRC Teensys, appear as a serial port and a generic HID device respectively, and so do not require a driver.

-We recommend the use of the [Zadig](https://zadig.akeo.ie/) utility. If you have set up the development environment with MSYS2, the QMK CLI installation script will have already installed the drivers for you.
+We recommend the use of the [Zadig](https://zadig.akeo.ie/) utility. If you have set up the development environment with MSYS2, the `qmk_install.sh` script will have already installed the drivers for you.

 ## Installation

@@ -22,7 +22,7 @@ If Zadig lists one or more devices with the `HidUsb` driver, your keyboard is pr

 If the arrow appears green, select the driver, and click **Install Driver**. See the [list of known bootloaders](#list-of-known-bootloaders) for the correct driver to install.

-![Zadig with a bootloader driver correctly installed](/b8VgXzx.png)
+![Zadig with a bootloader driver correctly installed](https://i.imgur.com/b8VgXzx.png)

 Finally, unplug and replug the keyboard to make sure the new driver has been loaded. If you are using the QMK Toolbox to flash, exit and restart it too, as it can sometimes fail to recognize the driver change.

@@ -30,15 +30,15 @@ Finally, unplug and replug the keyboard to make sure the new driver has been loa

 If you find that you can no longer type with the keyboard, you may have accidentally replaced the driver for the keyboard itself instead of for the bootloader. This can happen when the keyboard is not in the bootloader mode. You can easily confirm this in Zadig - a healthy keyboard has the `HidUsb` driver installed on all of its interfaces:

-![A healthy keyboard as seen by Zadig](/Hx0E5kC.png)
+![A healthy keyboard as seen by Zadig](https://i.imgur.com/Hx0E5kC.png)

 Open the Device Manager, select **View → Devices by container**, and look for an entry with your keyboard's name.

-![The board with the wrong driver installed, in Device Manager](/o7WLvBl.png)
+![The board with the wrong driver installed, in Device Manager](https://i.imgur.com/o7WLvBl.png)

 Right-click each entry and hit **Uninstall device**. Make sure to tick **Delete the driver software for this device** first if it appears.

-![The Device Uninstall dialog, with the "delete driver" checkbox ticked](/aEs2RuA.png)
+![The Device Uninstall dialog, with the "delete driver" checkbox ticked](https://i.imgur.com/aEs2RuA.png)

 Click **Action → Scan for hardware changes**. At this point, you should be able to type again. Double check in Zadig that the keyboard device(s) are using the `HidUsb` driver. If so, you're all done, and your board should be functional again! Otherwise, repeat this process until Zadig reports the correct driver.

@@ -54,11 +54,11 @@ Open the Device Manager, select **View → Devices by container**, and look for

 Find the `Inf name` value in the Details tab of the device properties. This should generally be something like `oemXX.inf`:

-![Device properties showing the Inf name value](/Bu4mk9m.png)
+![Device properties showing the Inf name value](https://i.imgur.com/Bu4mk9m.png)

 Then, open a new Command Prompt window as an Administrator (type in `cmd` into the Start menu and press Ctrl+Shift+Enter). Run `pnputil /enum-drivers` to verify the `Inf name` matches the `Published Name` field of one of the entries:

-![pnputil output with matching driver highlighted](/3RrSjzW.png)
+![pnputil output with matching driver highlighted](https://i.imgur.com/3RrSjzW.png)

 Run `pnputil /delete-driver oemXX.inf /uninstall`. This will delete the driver and remove it from any devices using it. Note that this will not uninstall the device itself.

@@ -221,31 +221,6 @@ Receive multiple bytes from the selected I2C device.

 ---

-### `i2c_status_t i2c_transmit_and_receive(uint8_t address, const uint8_t* tx_data, uint16_t tx_length, uint8_t* rx_data, uint16_t rx_length, uint16_t timeout)` {#api-i2c-transmit-and-receive}
-
-Send and receive multiple bytes from the selected I2C device.
-
-#### Arguments {#api-i2c-transmit-and-receive-arguments}
-
- - `uint8_t address`
-   The 7-bit I2C address of the device.
- - `const uint8_t* tx_data`
-   A pointer to the data to transmit.
- - `uint16_t tx_length`
-   The number of bytes to write. Take care not to overrun the length of `tx_data`.
- - `uint8_t* rx_data`
-   A pointer to a buffer to read into.
- - `uint16_t rx_length`
-   The number of bytes to read. Take care not to overrun the length of `data`.
- - `uint16_t timeout`
-   The time in milliseconds to wait for a response from the target device.
-
-#### Return Value {#api-i2c-transmit-and-receive-return}
-
-`I2C_STATUS_TIMEOUT` if the timeout period elapses, `I2C_STATUS_ERROR` if some other error occurs, otherwise `I2C_STATUS_SUCCESS`.
-
---
-
 ### `i2c_status_t i2c_write_register(uint8_t devaddr, uint8_t regaddr, const uint8_t* data, uint16_t length, uint16_t timeout)` {#api-i2c-write-register}

 Write to a register with an 8-bit address on the I2C device.
@@ -292,7 +292,7 @@ Set the color of a single LED. This function does not immediately update the LED

 ---

-### `void ws2812_set_color_all(uint8_t red, uint8_t green, uint8_t blue)` {#api-ws2812-set-color-all}
+### `void ws812_set_color_all(uint8_t red, uint8_t green, uint8_t blue)` {#api-ws2812-set-color-all}

 Set the color of all LEDs.

@@ -24,7 +24,7 @@ As its name implies Direct Pin works by connecting one switch per pin. The other

 Here is a schematic showing how we connect a single button to pin A3 on a ProMicro:

-![Schematic diagram showing a ProMicro with a wire coming out of A3, connecting to the left side of a switch. Another wire comes out of the right side of the switch to connect to the Ground Plane.](/JcDhZll.png)
+![Schematic diagram showing a ProMicro with a wire coming out of A3, connecting to the left side of a switch. Another wire comes out of the right side of the switch to connect to the Ground Plane.](https://i.imgur.com/JcDhZll.png)

 Once you have wired your switches you can assign keycodes to each pin and build a firmware by selecting the MCU you are using from the Keyboard dropdown. Use this link to show only Easy Maker Direct Pin:

@@ -44,7 +44,7 @@ Pro Micro (Atmega32u4), make sure to include `CONFIG_USB_ACM=y`. Other devices m

 Issues encountered when flashing keyboards on Windows are most often due to having the wrong drivers installed for the bootloader, or none at all.

-Re-running the QMK installation script (`curl -fsSL https://install.qmk.fm | sh`) or reinstalling the QMK Toolbox may fix the issue. Alternatively, you can download and run the [`qmk_driver_installer`](https://github.com/qmk/qmk_driver_installer) package manually.
+Re-running the QMK installation script (`./util/qmk_install.sh` from the `qmk_firmware` directory in MSYS2 or WSL) or reinstalling the QMK Toolbox may fix the issue. Alternatively, you can download and run the [`qmk_driver_installer`](https://github.com/qmk/qmk_driver_installer) package manually.

 If that doesn't work, then you may need to download and run Zadig. See [Bootloader Driver Installation with Zadig](driver_installation_zadig) for more detailed information.

@@ -13,7 +13,7 @@ Keycodes are actually defined in [quantum/keycode.h](https://github.com/qmk/qmk_
 There are 3 standard keyboard layouts in use around the world- ANSI, ISO, and JIS. North America primarily uses ANSI, Europe and Africa primarily use ISO, and Japan uses JIS. Regions not mentioned typically use either ANSI or ISO. The keycodes corresponding to these layouts are shown here:

 <!-- Source for this image: https://www.keyboard-layout-editor.com/#/gists/bf431647d1001cff5eff20ae55621e9a -->
-![Keyboard Layout Image](/5wsh5wM.png)
+![Keyboard Layout Image](https://i.imgur.com/5wsh5wM.png)

 ## How Can I Make Custom Names For Complex Keycodes?

@@ -2,22 +2,8 @@

 This page documents the automated process for converting keyboards to use drop-in replacement controllers. This process is designed to be easy to use and can be completed in a few simple steps.

-You can generate the firmware by appending `-e CONVERT_TO=<target>` to your compile/flash command. For example:
-
-```sh
-qmk flash -c -kb keebio/bdn9/rev1 -km default -e CONVERT_TO=proton_c
-```
-
-You can also configure this within your [keymap](#keymap) to accomplish the same thing.
-
-::: tip
-If you get build errors, you will need to convert the keyboard's code to be [compatible](#keyboard-req) with the converter feature, or provide additional [keymap](#keymap-add) configuration.
-:::
-
 ## Supported Converters

-Each converter category is broken down by its declared `pin compatibility`. This ensures that only valid combinations are attempted.
-
 The following converters are available at this time:

 | From       | To                |
@@ -42,56 +28,86 @@ The following converters are available at this time:
 | `elite_c`  | `helios`          |
 | `elite_c`  | `liatris`         |

-## Configuration

-Configuring a converter to use can be done by adding one of the following lines to your keymaps's configuration:
+## Overview

-:::::tabs
+Each converter category is broken down by its declared `pin compatibility`. This ensures that only valid combinations are attempted. You can generate the firmware by appending `-e CONVERT_TO=<target>` to your compile/flash command. For example:

-==== keymap.json
-
-```json [keymap.json]
-{
-    "version": 1,
-    "keyboard": "keebio/bdn9/rev1",
-    "keymap": "keebio_bdn9_rev1_layout_2025-05-20",
-    "converter": "proton_c", // [!code focus]
-    "layout": "LAYOUT",
-}
+```sh
+qmk flash -c -kb keebio/bdn9/rev1 -km default -e CONVERT_TO=proton_c
 ```

-==== rules.mk
-
-```makefile
-CONVERT_TO = proton_c
-```
-
-:::::
+You can also add the same `CONVERT_TO=<target>` to your keymap's `rules.mk`, which will accomplish the same thing.

 ::: tip
-If you get build errors, you will need to convert the keyboard's code to be [compatible](#keyboard-req) with the converter feature, or provide additional [keymap](#keymap-add) configuration.
+If you get errors about `PORTB/DDRB`, etc not being defined, you'll need to convert the keyboard's code to use the [GPIO Controls](drivers/gpio) that will work for both ARM and AVR. This shouldn't affect the AVR builds at all.
 :::

-## Pro Micro Converters
+### Conditional Configuration

-If a board currently supported by QMK uses a [Pro Micro](https://www.sparkfun.com/products/12640) (or compatible board), the supported alternative controllers are:
+Once a converter is enabled, it exposes the `CONVERT_TO_<target_uppercase>` flag that you can use in your code with `#ifdef`s, For example:

-| Device                                                                                   | Target            | CLI Argument                    | `rules.mk`                   | Condition                           |
-|------------------------------------------------------------------------------------------|-------------------|---------------------------------|------------------------------|-------------------------------------|
-| [Proton C](https://qmk.fm/proton-c/)                                                     | `proton_c`        | `-e CONVERT_TO=proton_c`        | `CONVERT_TO=proton_c`        | `#ifdef CONVERT_TO_PROTON_C`        |
-| [Adafruit KB2040](https://learn.adafruit.com/adafruit-kb2040)                            | `kb2040`          | `-e CONVERT_TO=kb2040`          | `CONVERT_TO=kb2040`          | `#ifdef CONVERT_TO_KB2040`          |
-| [SparkFun Pro Micro - RP2040](https://www.sparkfun.com/products/18288)                   | `sparkfun_pm2040` | `-e CONVERT_TO=sparkfun_pm2040` | `CONVERT_TO=sparkfun_pm2040` | `#ifdef CONVERT_TO_SPARKFUN_PM2040` |
-| [Blok](https://boardsource.xyz/store/628b95b494dfa308a6581622)                           | `blok`            | `-e CONVERT_TO=blok`            | `CONVERT_TO=blok`            | `#ifdef CONVERT_TO_BLOK`            |
-| [Bit-C PRO](https://nullbits.co/bit-c-pro)                                               | `bit_c_pro`       | `-e CONVERT_TO=bit_c_pro`       | `CONVERT_TO=bit_c_pro`       | `#ifdef CONVERT_TO_BIT_C_PRO`       |
-| [STeMCell](https://github.com/megamind4089/STeMCell)                                     | `stemcell`        | `-e CONVERT_TO=stemcell`        | `CONVERT_TO=stemcell`        | `#ifdef CONVERT_TO_STEMCELL`        |
-| [customMK Bonsai C4](https://shop.custommk.com/products/bonsai-c4-microcontroller-board) | `bonsai_c4`       | `-e CONVERT_TO=bonsai_c4`       | `CONVERT_TO=bonsai_c4`       | `#ifdef CONVERT_TO_BONSAI_C4`       |
-| [RP2040 Community Edition](#rp2040_ce)                                                   | `rp2040_ce`       | `-e CONVERT_TO=rp2040_ce`       | `CONVERT_TO=rp2040_ce`       | `#ifdef CONVERT_TO_RP2040_CE`       |
-| [Elite-Pi](https://keeb.io/products/elite-pi-usb-c-pro-micro-replacement-rp2040)         | `elite_pi`        | `-e CONVERT_TO=elite_pi`        | `CONVERT_TO=elite_pi`        | `#ifdef CONVERT_TO_ELITE_PI`        |
-| [0xCB Helios](https://keeb.supply/products/0xcb-helios)                                  | `helios`          | `-e CONVERT_TO=helios`          | `CONVERT_TO=helios`          | `#ifdef CONVERT_TO_HELIOS`          |
-| [Liatris](https://splitkb.com/products/liatris)                                          | `liatris`         | `-e CONVERT_TO=liatris`         | `CONVERT_TO=liatris`         | `#ifdef CONVERT_TO_LIATRIS`         |
-| [Imera](https://splitkb.com/products/imera)                                              | `imera`           | `-e CONVERT_TO=imera`           | `CONVERT_TO=imera`           | `#ifdef CONVERT_TO_IMERA`           |
-| [Michi](https://github.com/ci-bus/michi-promicro-rp2040)                                 | `michi`           | `-e CONVERT_TO=michi`           | `CONVERT_TO=michi`           | `#ifdef CONVERT_TO_MICHI`           |
-| [Svlinky](https://github.com/sadekbaroudi/svlinky)                                       | `svlinky`         | `-e CONVERT_TO=svlinky`         | `CONVERT_TO=svlinky`         | `#ifdef CONVERT_TO_SVLINKY`         |
+```c
+#ifdef CONVERT_TO_PROTON_C
+    // Proton C code
+#else
+    // Pro Micro code
+#endif
+```
+
+### Pin Compatibility
+
+To ensure compatibility, provide validation, and enable future workflows, a keyboard should declare its `pin compatibility`. For legacy reasons, this is currently assumed to be `promicro`. The following pin compatibility interfaces are currently defined:
+
+| Pin Compatibility | Notes                             |
+|-------------------|-----------------------------------|
+| `promicro`        | Includes RX/TX LEDs               |
+| `elite_c`         | Includes bottom row pins, no LEDs |
+
+To declare the base for conversions, add this line to your keyboard's `rules.mk`:
+
+```makefile
+PIN_COMPATIBLE = elite_c
+```
+
+## Pro Micro
+
+If a board currently supported in QMK uses a [Pro Micro](https://www.sparkfun.com/products/12640) (or compatible board), the supported alternative controllers are:
+
+| Device                                                                                   | Target            |
+|------------------------------------------------------------------------------------------|-------------------|
+| [Proton C](https://qmk.fm/proton-c/)                                                     | `proton_c`        |
+| [Adafruit KB2040](https://learn.adafruit.com/adafruit-kb2040)                            | `kb2040`          |
+| [SparkFun Pro Micro - RP2040](https://www.sparkfun.com/products/18288)                   | `sparkfun_pm2040` |
+| [Blok](https://boardsource.xyz/store/628b95b494dfa308a6581622)                           | `blok`            |
+| [Bit-C PRO](https://nullbits.co/bit-c-pro)                                               | `bit_c_pro`       |
+| [STeMCell](https://github.com/megamind4089/STeMCell)                                     | `stemcell`        |
+| [customMK Bonsai C4](https://shop.custommk.com/products/bonsai-c4-microcontroller-board) | `bonsai_c4`       |
+| [Elite-Pi](https://keeb.io/products/elite-pi-usb-c-pro-micro-replacement-rp2040)         | `elite_pi`        |
+| [0xCB Helios](https://keeb.supply/products/0xcb-helios)                                  | `helios`          |
+| [Liatris](https://splitkb.com/products/liatris)                                          | `liatris`         |
+| [Imera](https://splitkb.com/products/imera)                                              | `imera`           |
+| [Michi](https://github.com/ci-bus/michi-promicro-rp2040)                                 | `michi`           |
+| [Svlinky](https://github.com/sadekbaroudi/svlinky)                                       | `svlinky`         |
+
+Converter summary:
+
+| Target            | Argument                        | `rules.mk`                   | Condition                           |
+|-------------------|---------------------------------|------------------------------|-------------------------------------|
+| `proton_c`        | `-e CONVERT_TO=proton_c`        | `CONVERT_TO=proton_c`        | `#ifdef CONVERT_TO_PROTON_C`        |
+| `kb2040`          | `-e CONVERT_TO=kb2040`          | `CONVERT_TO=kb2040`          | `#ifdef CONVERT_TO_KB2040`          |
+| `sparkfun_pm2040` | `-e CONVERT_TO=sparkfun_pm2040` | `CONVERT_TO=sparkfun_pm2040` | `#ifdef CONVERT_TO_SPARKFUN_PM2040` |
+| `blok`            | `-e CONVERT_TO=blok`            | `CONVERT_TO=blok`            | `#ifdef CONVERT_TO_BLOK`            |
+| `bit_c_pro`       | `-e CONVERT_TO=bit_c_pro`       | `CONVERT_TO=bit_c_pro`       | `#ifdef CONVERT_TO_BIT_C_PRO`       |
+| `stemcell`        | `-e CONVERT_TO=stemcell`        | `CONVERT_TO=stemcell`        | `#ifdef CONVERT_TO_STEMCELL`        |
+| `bonsai_c4`       | `-e CONVERT_TO=bonsai_c4`       | `CONVERT_TO=bonsai_c4`       | `#ifdef CONVERT_TO_BONSAI_C4`       |
+| `rp2040_ce`       | `-e CONVERT_TO=rp2040_ce`       | `CONVERT_TO=rp2040_ce`       | `#ifdef CONVERT_TO_RP2040_CE`       |
+| `elite_pi`        | `-e CONVERT_TO=elite_pi`        | `CONVERT_TO=elite_pi`        | `#ifdef CONVERT_TO_ELITE_PI`        |
+| `helios`          | `-e CONVERT_TO=helios`          | `CONVERT_TO=helios`          | `#ifdef CONVERT_TO_HELIOS`          |
+| `liatris`         | `-e CONVERT_TO=liatris`         | `CONVERT_TO=liatris`         | `#ifdef CONVERT_TO_LIATRIS`         |
+| `imera`           | `-e CONVERT_TO=imera`           | `CONVERT_TO=imera`           | `#ifdef CONVERT_TO_IMERA`           |
+| `michi`           | `-e CONVERT_TO=michi`           | `CONVERT_TO=michi`           | `#ifdef CONVERT_TO_MICHI`           |
+| `svlinky`         | `-e CONVERT_TO=svlinky`         | `CONVERT_TO=svlinky`         | `#ifdef CONVERT_TO_SVLINKY`         |

 ### Proton C {#proton_c}

@@ -103,26 +119,26 @@ The Proton C only has one on-board LED (C13), and by default, the TXLED (D5) is

 The following defaults are based on what has been implemented for STM32 boards.

-| Feature                                    | Notes                                                                                                          |
-|--------------------------------------------|----------------------------------------------------------------------------------------------------------------|
-| [Audio](features/audio)                    | Enabled                                                                                                        |
-| [RGB Lighting](features/rgblight)          | Disabled                                                                                                       |
+| Feature                                      | Notes                                                                                                            |
+|----------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| [Audio](features/audio)                    | Enabled                                                                                                          |
+| [RGB Lighting](features/rgblight)          | Disabled                                                                                                         |
 | [Backlight](features/backlight)            | Forces [task driven PWM](features/backlight#software-pwm-driver) until ARM can provide automatic configuration |
-| USB Host (e.g. USB-USB converter)          | Not supported (USB host code is AVR specific and is not currently supported on ARM)                            |
-| [Split keyboards](features/split_keyboard) | Partial - heavily dependent on enabled features                                                                |
+| USB Host (e.g. USB-USB converter)            | Not supported (USB host code is AVR specific and is not currently supported on ARM)                              |
+| [Split keyboards](features/split_keyboard) | Partial - heavily dependent on enabled features                                                                  |

 ### Adafruit KB2040 {#kb2040}

 The following defaults are based on what has been implemented for [RP2040](platformdev_rp2040) boards.

-| Feature                                    | Notes                                                                                                          |
-|--------------------------------------------|----------------------------------------------------------------------------------------------------------------|
-| [RGB Lighting](features/rgblight)          | Enabled via `PIO` vendor driver                                                                                |
+| Feature                                      | Notes                                                                                                            |
+|----------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| [RGB Lighting](features/rgblight)          | Enabled via `PIO` vendor driver                                                                                  |
 | [Backlight](features/backlight)            | Forces [task driven PWM](features/backlight#software-pwm-driver) until ARM can provide automatic configuration |
-| USB Host (e.g. USB-USB converter)          | Not supported (USB host code is AVR specific and is not currently supported on ARM)                            |
-| [Split keyboards](features/split_keyboard) | Partial via `PIO` vendor driver - heavily dependent on enabled features                                        |
+| USB Host (e.g. USB-USB converter)            | Not supported (USB host code is AVR specific and is not currently supported on ARM)                              |
+| [Split keyboards](features/split_keyboard) | Partial via `PIO` vendor driver - heavily dependent on enabled features                                          |

-### SparkFun Pro Micro - RP2040, Blok, Bit-C PRO and Michi {#sparkfun_pm2040}
+### SparkFun Pro Micro - RP2040, Blok, Bit-C PRO and Michi {#sparkfun_pm2040 }

 Feature set is identical to [Adafruit KB2040](#kb2040).

@@ -161,193 +177,31 @@ Feature set is identical to [Adafruit KB2040](#kb2040). VBUS detection is enable

 Feature set is a pro micro equivalent of the [RP2040 Community Edition](#rp2040_ce), except that two of the analog GPIO have been replaced with digital only GPIO. These two were moved to the FPC connector to support the [VIK specification](https://github.com/sadekbaroudi/vik). This means that if you are expecting analog support on all 4 pins as provided on a RP2040 Community Edition pinout, you will not have that. Please see the [Svlinky github page](https://github.com/sadekbaroudi/svlinky) for more details.

-## Elite-C Converters
+## Elite-C

-If a board currently supported by QMK uses an [Elite-C](https://keeb.io/products/elite-c-low-profile-version-usb-c-pro-micro-replacement-atmega32u4), the supported alternative controllers are:
+If a board currently supported in QMK uses an [Elite-C](https://keeb.io/products/elite-c-low-profile-version-usb-c-pro-micro-replacement-atmega32u4), the supported alternative controllers are:

-| Device                                                                           | Target      | CLI Argument              | `rules.mk`             | Condition                     |
-|----------------------------------------------------------------------------------|-------------|---------------------------|------------------------|-------------------------------|
-| [STeMCell](https://github.com/megamind4089/STeMCell)                             | `stemcell`  | `-e CONVERT_TO=stemcell`  | `CONVERT_TO=stemcell`  | `#ifdef CONVERT_TO_STEMCELL`  |
-| [RP2040 Community Edition](#rp2040_ce_elite)                                     | `rp2040_ce` | `-e CONVERT_TO=rp2040_ce` | `CONVERT_TO=rp2040_ce` | `#ifdef CONVERT_TO_RP2040_CE` |
-| [Elite-Pi](https://keeb.io/products/elite-pi-usb-c-pro-micro-replacement-rp2040) | `elite_pi`  | `-e CONVERT_TO=elite_pi`  | `CONVERT_TO=elite_pi`  | `#ifdef CONVERT_TO_ELITE_PI`  |
-| [0xCB Helios](https://keeb.supply/products/0xcb-helios)                          | `helios`    | `-e CONVERT_TO=helios`    | `CONVERT_TO=helios`    | `#ifdef CONVERT_TO_HELIOS`    |
-| [Liatris](https://splitkb.com/products/liatris)                                  | `liatris`   | `-e CONVERT_TO=liatris`   | `CONVERT_TO=liatris`   | `#ifdef CONVERT_TO_LIATRIS`   |
+| Device                                                                           | Target            |
+|----------------------------------------------------------------------------------|-------------------|
+| [STeMCell](https://github.com/megamind4089/STeMCell)                             | `stemcell`        |
+| [Elite-Pi](https://keeb.io/products/elite-pi-usb-c-pro-micro-replacement-rp2040) | `elite_pi`        |
+| [0xCB Helios](https://keeb.supply/products/0xcb-helios)                          | `helios`          |
+| [Liatris](https://splitkb.com/products/liatris)                                  | `liatris`         |

-### STeMCell {#stemcell_elite}
+Converter summary:
+
+| Target            | Argument                        | `rules.mk`                   | Condition                           |
+|-------------------|---------------------------------|------------------------------|-------------------------------------|
+| `stemcell`        | `-e CONVERT_TO=stemcell`        | `CONVERT_TO=stemcell`        | `#ifdef CONVERT_TO_STEMCELL`        |
+| `rp2040_ce`       | `-e CONVERT_TO=rp2040_ce`       | `CONVERT_TO=rp2040_ce`       | `#ifdef CONVERT_TO_RP2040_CE`       |
+| `elite_pi`        | `-e CONVERT_TO=elite_pi`        | `CONVERT_TO=elite_pi`        | `#ifdef CONVERT_TO_ELITE_PI`        |
+| `helios`          | `-e CONVERT_TO=helios`          | `CONVERT_TO=helios`          | `#ifdef CONVERT_TO_HELIOS`          |
+| `liatris`         | `-e CONVERT_TO=liatris`         | `CONVERT_TO=liatris`         | `#ifdef CONVERT_TO_LIATRIS`         |
+
+### STeMCell {#stemcell}_elite

 Identical to [Pro Micro - STeMCell](#stemcell) with support for the additional bottom row of pins.

 ### RP2040 Community Edition {#rp2040_ce_elite}

 Identical to [Pro Micro - RP2040 Community Edition](#rp2040_ce) with support for the additional bottom row of pins.
-
-## Advanced Topics
-
-### Keyboard Configuration
-
-To configure a keyboard to allow the converter feature, add the following line to your keyboard's `.json` configuration:
-
-```json [keyboard.json]
-{
-    "maintainer": "QMK",
-    "development_board": "promicro", // [!code focus]
-    "diode_direction": "COL2ROW",
-}
-```
-
-See the [pin compatibility](#pin_compatible) for more information.
-
-#### Additional Requirements {#keyboard-req}
-
-Keyboards must use the platform agnostic abstractions provided by QMK. This includes:
-
-* Use of [GPIO Controls](drivers/gpio).
-
-### Additional Keymap Configuration {#keymap-add}
-
-While effort has been made to make converters as compatible as possible, sometimes additional platform specific configuration is required.
-
-For example, enabling hardware peripherals by adding a keymap level `mcuconf.h` with something like the following:
-```c
-#pragma once
-
-#include_next <mcuconf.h>
-
-#undef RP_SIO_USE_UART0
-#define RP_SIO_USE_UART0 TRUE
-```
-
-You can find details on how to configure drivers on their respective pages.
-
-Alternatively, you may have to disable incompatible features. For example:
-
-:::::tabs
-
-==== keymap.json
-
-```json [keymap.json]
-{
-    "version": 1,
-    "keyboard": "keebio/bdn9/rev1",
-    "keymap": "keebio_bdn9_rev1_layout_2025-05-20",
-    "converter": "proton_c",
-    "config": { // [!code focus]
-        "features": { // [!code focus]
-            "audio": false // [!code focus]
-        }
-    }
-    "layout": "LAYOUT",
-}
-```
-
-==== rules.mk
-
-```makefile
-AUDIO_ENABLE = no
-```
-
-:::::
-
-### Conditional Configuration
-
-Once a converter is enabled, it exposes the `CONVERT_TO_<target_uppercase>` flag that you can use in your code with `#ifdef`s, For example:
-
-```c
-#ifdef CONVERT_TO_PROTON_C
-    // Proton C code
-#else
-    // Pro Micro code
-#endif
-```
-
-### Pin Compatibility {#pin_compatible}
-
-To ensure compatibility, provide validation, and power future workflows, a keyboard should declare its `pin compatibility`. This ensures that only valid combinations are attempted.
-
-::: tip Note
-This will already be configured for you if are using the `promicro` development board preset.
-:::
-
-To declare the base interface for conversions, add the following line to your keyboard's configuration:
-
-```json [keyboard.json]
-{
-    "maintainer": "QMK",
-    "development_board": "elite_c", // [!code focus]
-    "pin_compatible": "elite_c", // [!code focus]
-    "diode_direction": "COL2ROW",
-}
-```
-
-The above example, configures a keyboard for a default of `elite_c` while allowing any of the `elite_c` converter targets.
-
-The framework then allows mapping of pins from `<PIN_COMPATIBLE>` to converter `<target>`.
-
-::: warning
-Mapped pins should adhere strictly to the defined interface, any extras present on the hardware should be ignored.
-:::
-
-#### Available Pin Compatibility
-
-:::::tabs
-
-==== promicro
-
-![promicro](/pin_compatible_promicro.svg)
-
-<!-- ```svgbob
-          pins
-     .-------------.           LEDs
-    |               |      _|_       _|_
-D3 -+-O             |      \ /B0     \ /D5
-D2 -+-O             |      -+-       -+-
-    |               |       |         |
-    |               |
-D1 -+-O           O-+- F4
-D0 -+-O           O-+- F5
-D4 -+-O           O-+- F6
-C6 -+-O           O-+- F7
-D7 -+-O           O-+- B1
-E6 -+-O           O-+- B3
-B4 -+-O           O-+- B2
-B5 -+-O           O-+- B6
-    |               |
-    '---+-+-+-+-+---'
-``` -->
-
-::: info Notes:
-Includes LEDs - these may be mapped to unused/unavailable pins when not present.
-:::
-
-==== elite_c
-
-![elite_c](/pin_compatible_elite_c.svg)
-
-<!-- ```svgbob
-          pins
-     .-------------.
-    |               |
-D3 -+-O             |
-D2 -+-O             |
-    |               |
-    |               |
-D1 -+-O           O-+- F4
-D0 -+-O           O-+- F5
-D4 -+-O           O-+- F6
-C6 -+-O           O-+- F7
-D7 -+-O           O-+- B1
-E6 -+-O           O-+- B3
-B4 -+-O           O-+- B2
-B5 -+-O O O O O O O-+- B6
-    |   | | | | |   |
-    '---+-+-+-+-+---'
-        + + + + +
-        B D C F F
-        7 5 7 1 0
-``` -->
-
-::: info Notes:
-Includes bottom row pins, no LEDs.
-:::
-
-:::::
@@ -8,7 +8,7 @@ The feature maintains a small buffer of recent key presses. On each key press, i

 The tricky part is how to efficiently check the buffer for typos. We don’t want to spend too much memory or time on storing or searching the typos. A good solution is to represent the typos with a trie data structure. A trie is a tree data structure where each node is a letter, and words are formed by following a path to one of the leaves.

-![An example trie](/HL5DP8H.png)
+![An example trie](https://i.imgur.com/HL5DP8H.png)

 Since we search whether the buffer ends in a typo, we store the trie writing in reverse. The trie is queried starting from the last letter, then second to last letter, and so on, until either a letter doesn’t match or we reach a leaf, meaning a typo was found.

@@ -279,7 +279,7 @@ All autocorrection data is stored in a single flat array autocorrect_data. Each
 * 01 ⇒ branching node: a trie node with multiple children.
 * 10 ⇒ leaf node: a leaf, corresponding to a typo and storing its correction.

-![An example trie](/HL5DP8H.png)
+![An example trie](https://i.imgur.com/HL5DP8H.png)

 **Branching node**. Each branch is encoded with one byte for the keycode (KC_A–KC_Z) followed by a link to the child node. Links between nodes are 16-bit byte offsets relative to the beginning of the array, serialized in little endian order.

@@ -227,7 +227,7 @@ In this typical example, the backlight LEDs are all connected in parallel toward
 A pulldown resistor is also placed between the gate pin and ground to keep it at a defined state when it is not otherwise being driven by the MCU.
 The values of these resistors are not critical - see [this Electronics StackExchange question](https://electronics.stackexchange.com/q/68748) for more information.

-![Backlight example circuit](/BmAvoUC.png)
+![Backlight example circuit](https://i.imgur.com/BmAvoUC.png)

 ## API {#api}

@@ -32,13 +32,12 @@ For the details about the internals of the dynamic macros, please read the comme

 There are a number of options added that should allow some additional degree of customization

-|Define                                    |Default         |Description                                                                                                      |
-|------------------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------|
-|`DYNAMIC_MACRO_SIZE`                      |128             |Sets the amount of memory that Dynamic Macros can use. This is a limited resource, dependent on the controller.  |
-|`DYNAMIC_MACRO_USER_CALL`                 |*Not defined*   |Defining this falls back to using the user `keymap.c` file to trigger the macro behavior.                        |
-|`DYNAMIC_MACRO_NO_NESTING`                |*Not Defined*   |Defining this disables the ability to call a macro from another macro (nested macros).                           |
-|`DYNAMIC_MACRO_DELAY`                     |*Not Defined*   |Sets the waiting time (ms unit) when sending each key.                                                           |
-|`DYNAMIC_MACRO_KEEP_ORIGINAL_LAYER_STATE` |*Not Defined*   |Defining this keeps the layer state when starting to record a macro                                              |
+|Define                      |Default         |Description                                                                                                      |
+|----------------------------|----------------|-----------------------------------------------------------------------------------------------------------------|
+|`DYNAMIC_MACRO_SIZE`        |128             |Sets the amount of memory that Dynamic Macros can use. This is a limited resource, dependent on the controller.  |
+|`DYNAMIC_MACRO_USER_CALL`   |*Not defined*   |Defining this falls back to using the user `keymap.c` file to trigger the macro behavior.                        |
+|`DYNAMIC_MACRO_NO_NESTING`  |*Not Defined*   |Defining this disables the ability to call a macro from another macro (nested macros).                           | 
+|`DYNAMIC_MACRO_DELAY`        |*Not Defined*   |Sets the waiting time (ms unit) when sending each key.                                                           |


 If the LEDs start blinking during the recording with each keypress, it means there is no more space for the macro in the macro buffer. To fit the macro in, either make the other macro shorter (they share the same buffer) or increase the buffer size by adding the `DYNAMIC_MACRO_SIZE` define in your `config.h` (default value: 128; please read the comments for it in the header).
@@ -14,7 +14,7 @@ You can use key overrides in a similar way to momentary layer/fn keys to activat

 To enable this feature, you need to add `KEY_OVERRIDE_ENABLE = yes` to your `rules.mk`.

-Then, in your `keymap.c` file, you'll need to define the `key_overrides` config. See below for more details.
+Then, in your `keymap.c` file, you'll need to define the array `key_overrides`, which defines all key overrides to be used. Each override is a value of type `key_override_t`. The array `key_overrides`contains pointers to `key_override_t` values (`const key_override_t **`).

 ## Creating Key Overrides {#creating-key-overrides}

@@ -35,12 +35,12 @@ layer.

 Consider a keymap with the following base layer.

-![Base layer with a MO(NAV) key.](/DkEhj9x.png)
+![Base layer with a MO(NAV) key.](https://i.imgur.com/DkEhj9x.png)

 The highlighted key is a momentary layer switch `MO(NAV)`. Holding it accesses a
 navigation layer.

-![Nav layer with a Layer Lock key.](/2wUZNWk.png)
+![Nav layer with a Layer Lock key.](https://i.imgur.com/2wUZNWk.png)


 Holding the NAV key is fine for brief use, but awkward to continue holding when
@@ -267,23 +267,6 @@ The paw 3204 sensor uses a serial type protocol for communication, and requires

 The CPI range is 400-1600, with supported values of (400, 500, 600, 800, 1000, 1200 and 1600).  Defaults to 1000 CPI.

-### PAW-3222 Sensor
-
-To use the PAW-3222 sensor, add this to your `rules.mk`:
-
-```make
-POINTING_DEVICE_DRIVER = paw3222
-```
-
-The following pins must be defined in `config.h`:
-
-| Setting (`config.h`)  | Description                                                        | Default                      |
-| --------------------- | ------------------------------------------------------------------ | ---------------------------- |
-| `PAW3222_CS_PIN`      | (Required) The pin connected to the chip select pin of the sensor. | `POINTING_DEVICE_CS_PIN`     |
-| `PAW3222_SPI_DIVISOR` | (Required) The SPI clock divisor. This is dependent on your MCU.   | _not defined_                |
-
-The CPI range is up to 4,000. Defaults to 1,000 CPI.
-
 ### Pimoroni Trackball

 To use the Pimoroni Trackball module, add this to your `rules.mk`:
@@ -55,7 +55,7 @@ Changing the **Hue** cycles around the circle.<br>
 Changing the **Saturation** moves between the inner and outer sections of the wheel, affecting the intensity of the color.<br>
 Changing the **Value** sets the overall brightness.<br>

-![QMK Color Wheel with HSV Values](/vkYVo66.jpg)
+![QMK Color Wheel with HSV Values](https://i.imgur.com/vkYVo66.jpg)

 ## Keycodes

@@ -91,11 +91,11 @@ SPLIT_TRANSPORT = custom

 Configuring your layout in a split keyboard works slightly differently to a non-split keyboard. Take for example the following layout. The top left numbers refer to the matrix row and column, and the bottom right are the order of the keys in the layout:

-![Physical layout](/QeY6kMQ.png)
+![Physical layout](https://i.imgur.com/QeY6kMQ.png)

 Since the matrix scanning procedure operates on entire rows, it first populates the left half's rows, then the right half's. Thus, the matrix as QMK views it has double the rows instead of double the columns:

-![Matrix](/4wjJzBU.png)
+![Matrix](https://i.imgur.com/4wjJzBU.png)

 ### Setting Handedness

@@ -497,7 +497,7 @@ Once you have done that, you will want to solder the diode from the 5V pad to th

 You may need to use the 5V pad from the regulator block above as the pads were too small and placed too closely together to place the Schottky diode properly.

-![Teensy++ 2.0](/BPEC5n5.jpg)
+![Teensy++ 2.0](https://i.imgur.com/BPEC5n5.png)

 ## Additional Resources

@@ -40,10 +40,6 @@ Similar to the first option, the second and third option are good for simple lay

 For more complicated cases, like blink the LEDs, fiddle with the backlighting, and so on, use the fourth or fifth option. Examples of each are listed below.

-::: tip 
-If too many tap dances are active at the same time, later ones won't have any effect. You need to increase `TAP_DANCE_MAX_SIMULTANEOUS` by adding `#define TAP_DANCE_MAX_SIMULTANEOUS 5` (or higher) to your keymap's `config.h` file if you expect that users may hold down many tap dance keys simultaneously. By default, only 3 tap dance keys can be used together at the same time.
-:::
-
 ## Implementation Details {#implementation}

 Well, that's the bulk of it! You should now be able to work through the examples below, and to develop your own Tap Dance functionality. But if you want a deeper understanding of what's going on behind the scenes, then read on for the explanation of how it all works!
@@ -213,13 +209,11 @@ tap_dance_action_t tap_dance_actions[] = {

 bool process_record_user(uint16_t keycode, keyrecord_t *record) {
    tap_dance_action_t *action;
-    tap_dance_state_t* state;

    switch (keycode) {
-        case TD(CT_CLN):
-            action = tap_dance_get(QK_TAP_DANCE_GET_INDEX(keycode));
-            state = tap_dance_get_state(QK_TAP_DANCE_GET_INDEX(keycode));
-            if (!record->event.pressed && state != NULL && state->count && !state->finished) {
+        case TD(CT_CLN): // list all tap dance keycodes with tap-hold configurations
+            action = &tap_dance_actions[QK_TAP_DANCE_GET_INDEX(keycode)];
+            if (!record->event.pressed && action->state.count && !action->state.finished) {
                tap_dance_tap_hold_t *tap_hold = (tap_dance_tap_hold_t *)action->user_data;
                tap_code16(tap_hold->tap);
            }
@@ -8,15 +8,15 @@ This guide assumes you're somewhat comfortable with running things at the comman

 Start on the [QMK GitHub page](https://github.com/qmk/qmk_firmware), and you'll see a button in the upper right that says "Fork":

-![Fork on GitHub](/8Toomz4.jpg)
+![Fork on GitHub](https://i.imgur.com/8Toomz4.jpg)

 If you're a part of an organization, you'll need to choose which account to fork it to. In most circumstances, you'll want to fork it to your personal account. Once your fork is completed (sometimes this takes a little while), click the "Clone or Download" button:

-![Download from GitHub](/N1NYcSz.jpg)
+![Download from GitHub](https://i.imgur.com/N1NYcSz.jpg)

 And be sure to select "HTTPS", and select the link and copy it:

-![HTTPS link](/eGO0ohO.jpg)
+![HTTPS link](https://i.imgur.com/eGO0ohO.jpg)

 From here, enter `git clone --recurse-submodules ` into the command line, and then paste your link:

@@ -57,10 +57,10 @@ To https://github.com/whoeveryouare/qmk_firmware.git

 Your changes now exist on your fork on GitHub - if you go back there (`https://github.com/<whoeveryouare>/qmk_firmware`), you can create a "New Pull Request" by clicking this button:

-![New Pull Request](/DxMHpJ8.jpg)
+![New Pull Request](https://i.imgur.com/DxMHpJ8.jpg)

 Here you'll be able to see exactly what you've committed - if it all looks good, you can finalize it by clicking "Create Pull Request":

-![Create Pull Request](/Ojydlaj.jpg)
+![Create Pull Request](https://i.imgur.com/Ojydlaj.jpg)

 After submitting, we may talk to you about your changes, ask that you make changes, and eventually accept it! Thanks for contributing to QMK :)
@@ -36,12 +36,12 @@ What you want to achieve is one leg from each switch being attached to the corre

 It is fairly simple to plan for an ortholinear keyboard (like a Planck).

-![Example Planck matrix](/FRShcLD.png)
+![Example Planck matrix](https://i.imgur.com/FRShcLD.png)
 Image from [RoastPotatoes' "How to hand wire a Planck"](https://blog.roastpotatoes.co/guide/2015/11/04/how-to-handwire-a-planck/)

 But the larger and more complicated your keyboard, the more complex the matrix.  [Keyboard Firmware Builder](https://kbfirmware.com/) can help you plan your matrix layout (shown here with a basic fullsize ISO keyboard imported from [Keyboard Layout Editor](https://www.keyboard-layout-editor.com).

-![Example ISO matrix](/UlJ4ZDP.png)
+![Example ISO matrix](https://i.imgur.com/UlJ4ZDP.png)

 Bear in mind that the number of rows plus the number of columns can not exceed the number of I/O pins on your controller.  So the fullsize matrix shown above would be possible on a Proton C or Teensy++, but not on a regular Teensy or Pro Micro.

@@ -51,14 +51,14 @@ Bear in mind that the number of rows plus the number of columns can not exceed t
 | :------------ |:-------------:| ------:| ------ |
 | Pro Micro*    | ATmega32u4    |     20 | [link](https://learn.sparkfun.com/tutorials/pro-micro--fio-v3-hookup-guide/hardware-overview-pro-micro#Teensy++_2.0)       |
 | Teensy 2.0    | ATmega32u4    |     25 | [link](https://www.pjrc.com/teensy/pinout.html)       |
-| [QMK Proton C](https://qmk.fm/proton-c/)      | STM32F303xC   |     36 | [link 1](https://qmk.fm/proton-c-pinout.jpg), [2](https://deskthority.net/wiki/QMK_Proton_C)       |
+| [QMK Proton C](https://qmk.fm/proton-c/)      | STM32F303xC   |     36 | [link 1](https://i.imgur.com/RhtrAlc.png), [2](https://deskthority.net/wiki/QMK_Proton_C)       |
 | Teensy++ 2.0  | AT90USB1286   |     46 | [link](https://www.pjrc.com/teensy/pinout.html#Teensy_2.0)       |

 *Elite C is essentially the same as a Pro Micro with a USB-C instead of Micro-USB

 There are also a number of boards designed specifically for handwiring that mount directly to a small number of switches and offer pinouts for the rest.  Though these are generally more expensive and may be more difficult to get hold of.

-<img src="/QiA3ta6.jpg" alt="Postage board mini mounted in place" width="500"/>
+<img src="https://i.imgur.com/QiA3ta6.jpg" alt="Postage board mini mounted in place" width="500"/>

 | Board         | Controller    | # I/O  |
 | :------------ |:-------------:| ------:|
@@ -74,13 +74,13 @@ Established materials and techniques include:

 | Technique     | Examples | Pros | Cons | Image
 | :-----------| :------- | :------ | :--- | :---
-| Lengths of wire with stripped segments | [Sasha Solomon's Dactyl](https://medium.com/@sachee/building-my-first-keyboard-and-you-can-too-512c0f8a4c5f) and [Cribbit's modern hand wire](https://geekhack.org/index.php?topic=87689.0) | Neat and tidy | Some effort in stripping the wire | ![Stripped wire](/0GNIYY0.jpg)
-| Short lengths of wire | [u/xicolinguada's ortho build](https://www.reddit.com/r/MechanicalKeyboards/comments/c39k4f/my_first_hand_wired_keyboard_its_not_perfect_but/) | Easier to strip the wire | More difficult to place | ![individual wire lengths](/mBe5vkL.jpg)
-| Magnet/Enamelled wire | [fknraiden's custom board](https://geekhack.org/index.php?topic=74223.0) | Can be directly soldered onto (insulation burns off with heat) | Appearance? | ![Magnet wire](/b4b7KDb.jpg)
-| Bending the legs of the diodes for the rows | [Matt3o's Brownfox](https://deskthority.net/viewtopic.php?f=7&t=6050) | Fewer solder joints required | Uninsulated | ![Bent diode legs](/aTnG8TV.jpg)
-| Using rigid wiring (e.g. brass tube) | [u/d_stilgar's invisible hardline](https://www.reddit.com/r/MechanicalKeyboards/comments/8aw5j2/invisible_hardline_keyboard_progress_update_april/) and [u/jonasfasler's first attempt](https://www.reddit.com/r/MechanicalKeyboards/comments/de1jyv/my_first_attempt_at_handwiring_a_keyboard/) | Very pretty | More difficult. No physical insulation | ![Hardline hand wire](/CnASmPo.jpg)
-| Bare wire with insulation added after (e.g. kapton tape) | [Matt3o's 65% on his website](https://matt3o.com/hand-wiring-a-custom-keyboard/) | Easier (no wire stripping required) | Not as attractive | ![Bare wire](/AvXZShD.jpg)
-| Copper tape | [ManuForm Dactyl](https://github.com/tshort/dactyl-keyboard) | Very easy | Only really works when your plate/case aligns with the bottom of your switches | ![Copper tape](/RFyNMlL.jpg)
+| Lengths of wire with stripped segments | [Sasha Solomon's Dactyl](https://medium.com/@sachee/building-my-first-keyboard-and-you-can-too-512c0f8a4c5f) and [Cribbit's modern hand wire](https://geekhack.org/index.php?topic=87689.0) | Neat and tidy | Some effort in stripping the wire | ![Stripped wire](https://i.imgur.com/0GNIYY0.jpg)
+| Short lengths of wire | [u/xicolinguada's ortho build](https://www.reddit.com/r/MechanicalKeyboards/comments/c39k4f/my_first_hand_wired_keyboard_its_not_perfect_but/) | Easier to strip the wire | More difficult to place | ![individual wire lengths](https://i.imgur.com/mBe5vkL.jpg)
+| Magnet/Enamelled wire | [fknraiden's custom board](https://geekhack.org/index.php?topic=74223.0) | Can be directly soldered onto (insulation burns off with heat) | Appearance? | ![Magnet wire](https://i.imgur.com/b4b7KDb.jpg)
+| Bending the legs of the diodes for the rows | [Matt3o's Brownfox](https://deskthority.net/viewtopic.php?f=7&t=6050) | Fewer solder joints required | Uninsulated | ![Bent diode legs](https://i.imgur.com/aTnG8TV.jpg)
+| Using rigid wiring (e.g. brass tube) | [u/d_stilgar's invisible hardline](https://www.reddit.com/r/MechanicalKeyboards/comments/8aw5j2/invisible_hardline_keyboard_progress_update_april/) and [u/jonasfasler's first attempt](https://www.reddit.com/r/MechanicalKeyboards/comments/de1jyv/my_first_attempt_at_handwiring_a_keyboard/) | Very pretty | More difficult. No physical insulation | ![Hardline hand wire](https://i.imgur.com/CnASmPo.jpg)
+| Bare wire with insulation added after (e.g. kapton tape) | [Matt3o's 65% on his website](https://matt3o.com/hand-wiring-a-custom-keyboard/) | Easier (no wire stripping required) | Not as attractive | ![Bare wire](https://i.imgur.com/AvXZShD.jpg)
+| Copper tape | [ManuForm Dactyl](https://github.com/tshort/dactyl-keyboard) | Very easy | Only really works when your plate/case aligns with the bottom of your switches | ![Copper tape](https://i.imgur.com/RFyNMlL.jpg)


 Note that these methods can be combined.  Prepare your lengths of wire before moving on to soldering.
@@ -97,11 +97,11 @@ There are a lot of soldering guides and tips available elsewhere but here are so

 To ensure a strong solder joint you want a good amount of contact between the solder and the two pieces of metal you are connecting. A good way of doing this (though not required) is looping around pins or twisting wires together before applying solder.

-<img src="/eHJjmnU.jpg" alt="Looped around rod" width="400"/>
+<img src="https://i.imgur.com/eHJjmnU.jpg" alt="Looped around rod" width="200"/> <img src="https://i.imgur.com/8nbxmmr.jpg?1" alt="Looped diode leg" width="200"/>

 If your diodes are on a packaging strip and need a bend in them (either the start of a loop or for connecting to its neighbour) this can easily done by bending it over something straight like the edge of a box, table, or ruler.  This also helps keep track of the direction of the diode as all the bends will be on the same side.

-<img src="/oITudbX.jpg" alt="Bent diode legs" width="400"/>
+<img src="https://i.imgur.com/oITudbX.jpg" alt="Bent diode legs" width="200"/>

 If your iron has temperature control, set it to 315ºC (600ºF).

@@ -164,7 +164,7 @@ Cut wires to the length of the distance from the a point on each column/row to t

 Ribbon cable can be used to keep this extra tidy.  You may also want to consider routing the wires beneath the existing columns/rows.

-<img src="/z2QlKfB.jpg" alt="Ribbon Cable" width="600"/>
+<img src="https://i.imgur.com/z2QlKfB.jpg" alt="Ribbon Cable" width="350"/>

 As you solder the wires to the controller make a note of which row/column is going to which pin on the controller as we'll use this data to setup the matrix when we create the firmware.

@@ -1,6 +1,6 @@
 # QMK Configurator

-[![QMK Configurator Screenshot](/anw9cOL.png)](https://config.qmk.fm/)
+[![QMK Configurator Screenshot](https://i.imgur.com/anw9cOL.png)](https://config.qmk.fm/)

 The [QMK Configurator](https://config.qmk.fm) is an online graphical user interface that generates QMK Firmware `.hex` or `.bin` files.

@@ -32,11 +32,11 @@ Building locally has a much shorter turnaround time than waiting for GitHub Acti

 A basic skeleton External Userspace repository can be found [here](https://github.com/qmk/qmk_userspace). If you wish to keep your keymaps on GitHub (strongly recommended!), you can fork the repository and use it as a base:

-![Userspace Fork](/hcegguh.png)
+![Userspace Fork](https://i.imgur.com/hcegguh.png)

 Going ahead with your fork will copy it to your account, at which point you can clone it to your local machine and begin adding your keymaps:

-![Userspace Clone](/CWYmsk8.png)
+![Userspace Clone](https://i.imgur.com/CWYmsk8.png)

 ```sh
 cd $HOME
@@ -99,8 +99,8 @@ All firmware builds you've added to the External Userspace build targets will be

 GitHub Actions can be used to automatically build your keymaps whenever you push changes to your External Userspace repository. If you have set up your list of build targets, this is as simple as enabling workflows in the GitHub repository settings:

-![Repo Settings](/EVkxOt1.png)
+![Repo Settings](https://i.imgur.com/EVkxOt1.png)

 Any push will result in compilation of all configured builds, and once completed a new release containing the newly-minted firmware files will be created on GitHub, which you can subsequently download and flash to your keyboard:

-![Releases](/zmwOL5P.png)
+![Releases](https://i.imgur.com/zmwOL5P.png)
@@ -50,64 +50,90 @@ You will need to install [MSYS2](https://www.msys2.org). Once installed, close a
 Install the QMK CLI by running:

 ```sh
-curl -fsSL https://install.qmk.fm | sh
+pacman --needed --noconfirm --disable-download-timeout -S git mingw-w64-x86_64-python-qmk
 ```

 ::::

 ==== macOS

+QMK maintains a Homebrew tap and formula which will automatically install the CLI and all necessary dependencies.
+
 #### Prerequisites

 You will need to install Homebrew. Follow the instructions on https://brew.sh.

+::: tip
+If you are using an Apple Silicon machine, the installation process will take significantly longer because GitHub actions do not have native runners to build binary packages for the ARM and AVR toolchains.
+:::
+
 #### Installation

 Install the QMK CLI by running:

 ```sh
-curl -fsSL https://install.qmk.fm | sh
+brew install qmk/qmk/qmk
 ```

 ==== Linux/WSL

-#### Installation
-
-::: info
-Many Linux distributions are supported, but not all. Mainstream distributions will have best success -- if possible, choose either Debian or its derivatives (such as Ubuntu, or Mint), CentOS or its derivatives (such as Fedora, or Rocky Linux), and Arch or its derivatives (such as Manjaro, or CachyOS).
-:::
-
-Install the QMK CLI by running:
-
-```sh
-curl -fsSL https://install.qmk.fm | sh
-```
-
 ::: tip
 **Note for WSL users**: By default, the installation process will clone the QMK repository into your WSL home directory, but if you have cloned manually, ensure that it is located inside the WSL instance instead of the Windows filesystem (ie. not in `/mnt`), as accessing it is currently [extremely slow](https://github.com/microsoft/WSL/issues/4197).
 :::

-::: warning
-Any QMK packages provided by your distribution's package manager are almost certainly out of date. It is strongly suggested the installation script above is used instead.
-:::
+#### Prerequisites
+
+You will need to install Git and Python. It's very likely that you already have both, but if not, one of the following commands should install them:
+
+* Debian / Ubuntu / Devuan: `sudo apt install -y git python3-pip`
+* Fedora / Red Hat / CentOS: `sudo yum -y install git python3-pip`
+* Arch / Manjaro: `sudo pacman --needed --noconfirm -S git python-pip libffi`
+* Void: `sudo xbps-install -y git python3-pip`
+* Solus: `sudo eopkg -y install git python3`
+* Sabayon: `sudo equo install dev-vcs/git dev-python/pip`
+* Gentoo: `sudo emerge dev-vcs/git dev-python/pip`
+
+#### Installation
+
+Install the QMK CLI by running:
+
+```sh
+python3 -m pip install --user qmk
+```
+
+Alternatively, install the QMK CLI as a [uv](https://docs.astral.sh/uv/) managed tool, kept isolated in a virtual environment (requires uv to be installed):
+
+```sh
+uv tool install qmk
+```
+
+#### Community Packages
+
+These packages are maintained by community members, so may not be up to date or completely functional. If you encounter problems, please report them to their respective maintainers.
+
+On Arch-based distros you can install the CLI from the official repositories (NOTE: at the time of writing this package marks some dependencies as optional that should not be):
+
+```sh
+sudo pacman -S qmk
+```
+
+You can also try the `qmk-git` package from AUR:
+
+```sh
+yay -S qmk-git
+```

 ==== FreeBSD

 #### Installation

-::: warning
-FreeBSD support is provided on a best-effort basis by the community instead of the QMK maintainers. It is strongly suggested that you use either Windows, macOS, or a supported distribution of Linux instead.
-:::
-
 Install the FreeBSD package for QMK CLI by running:

 ```sh
 pkg install -g "py*-qmk"
 ```

-::: info NOTE
-Remember to follow the instructions printed at the end of installation (use `pkg info -Dg "py*-qmk"` to show them again).
-:::
+NOTE: remember to follow the instructions printed at the end of installation (use `pkg info -Dg "py*-qmk"` to show them again).

 :::::

@@ -66,7 +66,7 @@ Once both plugins are installed, restart Eclipse as prompted.
  * Select the _AVR-GCC Toolchain_;
  * Keep the rest as-is and click <kbd>Finish</kbd>

-  ![Importing QMK in Eclipse](/oHYR1yW.png)
+  ![Importing QMK in Eclipse](https://i.imgur.com/oHYR1yW.png)

 3. The project will now be loaded and indexed. Its files can be browsed easily through the _Project Explorer_ on the left.

@@ -174,7 +174,7 @@ You'll need to perform some modifications to the file above in order to target y
 * `"armToolchainPath"`: _[Optional]_ The path to the ARM toolchain installation location on Windows -- under normal circumstances Linux/macOS will auto-detect this correctly and will not need to be specified. 

 ::: warning
-Windows builds of QMK Firmware are generally compiled using QMK MSYS, and the path to gdb's location (`C:\\QMK_MSYS\\mingw64\\bin`) needs to be specified under `armToolchainPath` for it to be detected. You may also need to change the GDB path to point at `C:\\QMK_MSYS\\mingw64\\bin\\gdb-multiarch.exe` in the VSCode Cortex-Debug user settings: ![VSCode Settings](/EGrPM1L.png)
+Windows builds of QMK Firmware are generally compiled using QMK MSYS, and the path to gdb's location (`C:\\QMK_MSYS\\mingw64\\bin`) needs to be specified under `armToolchainPath` for it to be detected. You may also need to change the GDB path to point at `C:\\QMK_MSYS\\mingw64\\bin\\gdb-multiarch.exe` in the VSCode Cortex-Debug user settings: ![VSCode Settings](https://i.imgur.com/EGrPM1L.png)
 :::

 The following modifications must be made to the keyboard's `rules.mk` file to enable debug information and disable optimisations -- this will ensure breakpoints and variable viewing works correctly:
@@ -7,7 +7,7 @@ The WeAct Blackpill is a popular choice for handwired boards, as it offers a pow
 * [WeAct GitHub for F4x1 Blackpill](https://github.com/WeActStudio/WeActStudio.MiniSTM32F4x1)
  * Unfortunately, due to supply issues official WeAct F411 based blackpills may not be available.

-![Blackpill F411](/nCgeolTh.png)
+![Blackpill F411](https://i.imgur.com/nCgeolTh.png)


 ## Pin Usage Limitations
@@ -2,7 +2,7 @@

 The Proton C is an Arm STM32F303xC based drop-in replacement for the Pro Micro.

-<img src="https://qmk.fm/proton-c.jpg" alt="Proton C" width="800"/>
+<img src="https://i.imgur.com/GdsN1Rdh.jpg" alt="Proton C" />

 #### Features

@@ -17,8 +17,8 @@ The following table shows the current driver status for peripherals on RP2040 MC

 ## GPIO

-<img alt="Raspberry Pi Pico pinout" src="/nLaiYDE.jpg" width="48%"/>
-<img alt="Sparkfun RP2040 Pro Micro pinout" src="/1TPAhrs.jpg" width="48%"/>
+<img alt="Raspberry Pi Pico pinout" src="https://i.imgur.com/nLaiYDE.jpg" width="48%"/>
+<img alt="Sparkfun RP2040 Pro Micro pinout" src="https://i.imgur.com/1TPAhrs.jpg" width="48%"/>

 ::: warning
 The GPIO pins of the RP2040 are not 5V tolerant!
--- a/Show More
+++ b/Show More