Deploying to gh-pages from @ qmk/qmk_firmware@39324e642f 🚀

assets/app.BQjPZ5OS.js

@@ -1,5 +1,5 @@
 import { V as inBrowser, a9 as useUpdateHead, aa as RouterSymbol, ab as initData, ac as dataSymbol, ad as Content, ae as ClientOnly, af as siteDataRef, ag as createSSRApp, ah as createRouter, ai as pathToFile, Y as __vitePreload, d as defineComponent, u as useData, k as onMounted, y as watchEffect, aj as usePrefetch, ak as useCopyCode, al as useCodeGroups, am as h } from "./chunks/framework.DyMmIvSC.js";
-import { R as RawTheme } from "./chunks/theme.Dtf33puR.js";
+import { R as RawTheme } from "./chunks/theme.BEU6ITQ7.js";
 function resolveThemeExtends(theme) {
   if (theme.extends) {
     const base = resolveThemeExtends(theme.extends);

assets/breaking_changes_instructions.md.C99NYDjO.js

@@ -1,7 +1,7 @@
 import { _ as _export_sfc, c as createElementBlock, o as openBlock, a8 as createStaticVNode } from "./chunks/framework.DyMmIvSC.js";
 const __pageData = JSON.parse('{"title":"Breaking Changes: My Pull Request Was Flagged","description":"","frontmatter":{},"headers":[],"relativePath":"breaking_changes_instructions.md","filePath":"breaking_changes_instructions.md"}');
 const _sfc_main = { name: "breaking_changes_instructions.md" };
-const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="breaking-changes-my-pull-request-was-flagged" tabindex="-1">Breaking Changes: My Pull Request Was Flagged <a class="header-anchor" href="#breaking-changes-my-pull-request-was-flagged" aria-label="Permalink to &quot;Breaking Changes: My Pull Request Was Flagged&quot;">​</a></h1><p>A QMK member may have replied to your pull request stating that your submission is a breaking change. In their judgment, the changes you have proposed have greater implications for either QMK, or its users.</p><p>Some things that may cause a pull request to be flagged are:</p><ul><li><strong>Edits to User Keymaps</strong> A user may submit their keymap to QMK, then some time later open a pull request with further updates, only to find it can&#39;t be merged because it was edited in the <code>qmk/qmk_firmware</code> repository. As not all users are proficient at using Git or GitHub, the user may find themself unable to fix the issue on their own.</li><li><strong>Changes to Expected Behavior</strong> Changes to QMK behavior may cause users to believe their hardware or QMK is broken if they flash new firmware that incorporates changes to existing QMK features, and find themselves without a means to restore the desired behavior.</li><li><strong>Changes Requiring User Action</strong> Changes may also require action to be taken by users, such as updating a toolchain or taking some action in Git.</li><li><strong>Changes Necessitating Increased Scrutiny</strong> On occasion, a submission may have implications for QMK as a project. This could be copyright/licensing issues, coding conventions, large feature overhauls, &quot;high-risk&quot; changes that need wider testing by our community, or something else entirely.</li><li><strong>Changes Requiring Communication to End Users</strong> This includes warnings about future deprecations, outdated practices, and anything else that needs to be communicated but doesn&#39;t fit into one of the above categories.</li></ul><h2 id="what-do-i-do" tabindex="-1">What Do I Do? <a class="header-anchor" href="#what-do-i-do" aria-label="Permalink to &quot;What Do I Do?&quot;">​</a></h2><p>If it is determined that your submission is a breaking change, there are a few things you can do to smooth the process:</p><h3 id="consider-splitting-up-your-pr" tabindex="-1">Consider Splitting Up Your PR <a class="header-anchor" href="#consider-splitting-up-your-pr" aria-label="Permalink to &quot;Consider Splitting Up Your PR&quot;">​</a></h3><p>If you are contributing core code, and the only reason it needs to go through breaking changes is that you are updating keymaps to match your change, consider whether you can submit your feature in a way that the old keymaps continue to work. Then submit a separate PR that goes through the breaking changes process to remove the old code.</p><h3 id="document-your-changes" tabindex="-1">Document Your Changes <a class="header-anchor" href="#document-your-changes" aria-label="Permalink to &quot;Document Your Changes&quot;">​</a></h3><p>Understanding the purpose for your submission, and possible implications or actions it will require can make the review process more straightforward. A changelog may suffice for this purpose, but more extensive changes may require a level of detail that is ill-suited for a changelog.</p><p>Commenting on your pull request and being responsive to questions, comments, and change requests is much appreciated.</p><h3 id="ask-for-help" tabindex="-1">Ask for Help <a class="header-anchor" href="#ask-for-help" aria-label="Permalink to &quot;Ask for Help&quot;">​</a></h3><p>Having your submission flagged may have caught you off guard. If you find yourself intimidated or overwhelmed, let us know. Comment on your pull request, or <a href="https://discord.gg/Uq7gcHh" target="_blank" rel="noreferrer">reach out to the QMK team on Discord</a>.</p>', 13);
+const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="breaking-changes-my-pull-request-was-flagged" tabindex="-1">Breaking Changes: My Pull Request Was Flagged <a class="header-anchor" href="#breaking-changes-my-pull-request-was-flagged" aria-label="Permalink to &quot;Breaking Changes: My Pull Request Was Flagged&quot;">​</a></h1><p>A QMK member may have replied to your pull request stating that your submission is a breaking change. In their judgment, the changes you have proposed have greater implications for either QMK, or its users.</p><p>Some things that may cause a pull request to be flagged are:</p><ul><li><strong>Edits to User Keymaps</strong> A user may submit their keymap to QMK, then some time later open a pull request with further updates, only to find it can&#39;t be merged because it was edited in the <code>qmk/qmk_firmware</code> repository. As not all users are proficient at using Git or GitHub, the user may find themself unable to fix the issue on their own.</li><li><strong>Changes to Expected Behavior</strong> Changes to QMK behavior may cause users to believe their hardware or QMK is broken if they flash new firmware that incorporates changes to existing QMK features, and find themselves without a means to restore the desired behavior.</li><li><strong>Changes Requiring User Action</strong> Changes may also require action to be taken by users, such as updating a toolchain or taking some action in Git.</li><li><strong>Changes Necessitating Increased Scrutiny</strong> On occasion, a submission may have implications for QMK as a project. This could be copyright/licensing issues, coding conventions, large feature overhauls, &quot;high-risk&quot; changes that need wider testing by our community, or something else entirely.</li><li><strong>Changes Requiring Communication to End Users</strong> This includes warnings about future deprecations, outdated practices, and anything else that needs to be communicated but doesn&#39;t fit into one of the above categories.</li></ul><h2 id="what-do-i-do" tabindex="-1">What Do I Do? <a class="header-anchor" href="#what-do-i-do" aria-label="Permalink to &quot;What Do I Do?&quot;">​</a></h2><p>If it is determined that your submission is a breaking change, there are a few things you can do to smooth the process:</p><h3 id="consider-splitting-up-your-pr" tabindex="-1">Consider Splitting Up Your PR <a class="header-anchor" href="#consider-splitting-up-your-pr" aria-label="Permalink to &quot;Consider Splitting Up Your PR&quot;">​</a></h3><p>If you are contributing core code, and the only reason it needs to go through breaking changes is that you are updating keymaps to match your change, consider whether you can submit your feature in a way that the old keymaps continue to work. Then submit a separate PR that goes through the breaking changes process to remove the old code.</p><h3 id="document-your-changes" tabindex="-1">Document Your Changes <a class="header-anchor" href="#document-your-changes" aria-label="Permalink to &quot;Document Your Changes&quot;">​</a></h3><p>Understanding the purpose for your submission, and possible implications or actions it will require can make the review process more straightforward. A changelog may suffice for this purpose, but more extensive changes may require a level of detail that is ill-suited for a changelog.</p><p>Commenting on your pull request and being responsive to questions, comments, and change requests is much appreciated.</p><h3 id="ask-for-help" tabindex="-1">Ask for Help <a class="header-anchor" href="#ask-for-help" aria-label="Permalink to &quot;Ask for Help&quot;">​</a></h3><p>Having your submission flagged may have caught you off guard. If you find yourself intimidated or overwhelmed, let us know. Comment on your pull request, or <a href="https://discord.gg/qmk" target="_blank" rel="noreferrer">reach out to the QMK team on Discord</a>.</p>', 13);
 const _hoisted_14 = [
   _hoisted_1
 ];

assets/chunks/VPLocalSearchBox.DwLVHdcz.js

@@ -5,8 +5,8 @@ var __publicField = (obj, key, value) => {
   return value;
 };
 import { Y as __vitePreload, j as ref, x as watch, an as unrefElement, ao as tryOnScopeDispose, d as defineComponent, G as shallowRef, ap as computedAsync, h as computed, aq as useSessionStorage, ar as useLocalStorage, y as watchEffect, as as watchDebounced, k as onMounted, S as nextTick, R as onKeyStroke, a6 as useRouter, at as useEventListener, Z as useScrollLock, V as inBrowser, au as onBeforeUnmount, o as openBlock, b as createBlock, l as createBaseVNode, a2 as withModifiers, m as unref, av as withDirectives, aw as vModelText, ax as isRef, c as createElementBlock, n as normalizeClass, e as createCommentVNode, E as renderList, F as Fragment, a as createTextVNode, t as toDisplayString, ay as Teleport, p as pushScopeId, q as popScopeId, az as markRaw, aA as createApp, ac as dataSymbol, ai as pathToFile, aB as escapeRegExp, _ as _export_sfc } from "./framework.DyMmIvSC.js";
-import { u as useData, c as createSearchTranslate } from "./theme.Dtf33puR.js";
-const localSearchIndex = { "root": () => __vitePreload(() => import("./@localSearchIndexroot.DRxWZfqC.js"), true ? [] : void 0) };
+import { u as useData, c as createSearchTranslate } from "./theme.BEU6ITQ7.js";
+const localSearchIndex = { "root": () => __vitePreload(() => import("./@localSearchIndexroot.DdHZIsf0.js"), true ? [] : void 0) };
 /*!
 * tabbable 6.2.0
 * @license MIT, https://github.com/focus-trap/tabbable/blob/master/LICENSE

assets/chunks/theme.BEU6ITQ7.js

@@ -1,4 +1,4 @@
-const __vite__fileDeps=["assets/chunks/VPLocalSearchBox.Ddh8XTZ_.js","assets/chunks/framework.DyMmIvSC.js"],__vite__mapDeps=i=>i.map(i=>__vite__fileDeps[i]);
+const __vite__fileDeps=["assets/chunks/VPLocalSearchBox.DwLVHdcz.js","assets/chunks/framework.DyMmIvSC.js"],__vite__mapDeps=i=>i.map(i=>__vite__fileDeps[i]);
 import { d as defineComponent, o as openBlock, c as createElementBlock, r as renderSlot, n as normalizeClass, a as createTextVNode, t as toDisplayString, b as createBlock, w as withCtx, e as createCommentVNode, T as Transition, _ as _export_sfc, u as useData$1, i as isExternal, f as treatAsHtml, g as withBase, h as computed, j as ref, k as onMounted, l as createBaseVNode, m as unref, p as pushScopeId, q as popScopeId, s as isActive, v as useMediaQuery, x as watch, y as watchEffect, z as onUnmounted, A as watchPostEffect, B as onUpdated, C as getScrollOffset, D as resolveComponent, F as Fragment, E as renderList, G as shallowRef, H as onContentUpdated, I as createVNode, J as resolveDynamicComponent, K as EXTERNAL_URL_RE, L as useRoute, M as mergeProps, N as inject, O as useWindowSize, P as normalizeStyle, Q as onClickOutside, R as onKeyStroke, S as nextTick, U as useWindowScroll, V as inBrowser, W as readonly, X as defineAsyncComponent, Y as __vitePreload, Z as useScrollLock, $ as provide, a0 as toHandlers, a1 as withKeys, a2 as withModifiers, a3 as useSlots, a4 as reactive, a5 as toRef, a6 as useRouter, a7 as onBeforeMount } from "./framework.DyMmIvSC.js";
 const _sfc_main$Z = /* @__PURE__ */ defineComponent({
   __name: "VPBadge",
@@ -2225,7 +2225,7 @@ const _hoisted_3$6 = {
 const _sfc_main$l = /* @__PURE__ */ defineComponent({
   __name: "VPNavBarSearch",
   setup(__props) {
-    const VPLocalSearchBox = defineAsyncComponent(() => __vitePreload(() => import("./VPLocalSearchBox.Ddh8XTZ_.js"), true ? __vite__mapDeps([0,1]) : void 0));
+    const VPLocalSearchBox = defineAsyncComponent(() => __vitePreload(() => import("./VPLocalSearchBox.DwLVHdcz.js"), true ? __vite__mapDeps([0,1]) : void 0));
     const VPAlgoliaSearchBox = () => null;
     const { theme: theme2 } = useData();
     const loaded = ref(false);

assets/index.md.BFvlZFTs.js

@@ -1,7 +1,7 @@
 import { _ as _export_sfc, c as createElementBlock, o as openBlock, a8 as createStaticVNode } from "./chunks/framework.DyMmIvSC.js";
 const __pageData = JSON.parse('{"title":"Quantum Mechanical Keyboard Firmware","description":"","frontmatter":{},"headers":[],"relativePath":"index.md","filePath":"index.md"}');
 const _sfc_main = { name: "index.md" };
-const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="quantum-mechanical-keyboard-firmware" tabindex="-1">Quantum Mechanical Keyboard Firmware <a class="header-anchor" href="#quantum-mechanical-keyboard-firmware" aria-label="Permalink to &quot;Quantum Mechanical Keyboard Firmware&quot;">​</a></h1><h2 id="what-is-qmk-firmware" tabindex="-1">What is QMK Firmware? <a class="header-anchor" href="#what-is-qmk-firmware" aria-label="Permalink to &quot;What is QMK Firmware?&quot;">​</a></h2><p>QMK (<em>Quantum Mechanical Keyboard</em>) is an open source community centered around developing computer input devices. The community encompasses all sorts of input devices, such as keyboards, mice, and MIDI devices. A core group of collaborators maintains <a href="https://github.com/qmk/qmk_firmware" target="_blank" rel="noreferrer">QMK Firmware</a>, <a href="https://config.qmk.fm" target="_blank" rel="noreferrer">QMK Configurator</a>, <a href="https://github.com/qmk/qmk_toolbox" target="_blank" rel="noreferrer">QMK Toolbox</a>, <a href="https://qmk.fm" target="_blank" rel="noreferrer">qmk.fm</a>, and this documentation with the help of community members like you.</p><h2 id="get-started" tabindex="-1">Get Started <a class="header-anchor" href="#get-started" aria-label="Permalink to &quot;Get Started&quot;">​</a></h2><div class="tip custom-block"><p class="custom-block-title">Basic</p><p><a href="./newbs_building_firmware_configurator">QMK Configurator</a></p><p>User friendly graphical interfaces, no programming knowledge required.</p></div><div class="warning custom-block"><p class="custom-block-title">Advanced</p><p><a href="./newbs">Use The Source</a></p><p>More powerful, but harder to use.</p></div><h2 id="make-it-yours" tabindex="-1">Make It Yours <a class="header-anchor" href="#make-it-yours" aria-label="Permalink to &quot;Make It Yours&quot;">​</a></h2><p>QMK has lots of features to explore, and a good deal of reference documentation to dig through. Most features are taken advantage of by modifying your <a href="./keymap">keymap</a>, and changing the <a href="./keycodes">keycodes</a>.</p><h2 id="need-help" tabindex="-1">Need help? <a class="header-anchor" href="#need-help" aria-label="Permalink to &quot;Need help?&quot;">​</a></h2><p>Check out the <a href="./support">support page</a> to see how you can get help using QMK.</p><h2 id="give-back" tabindex="-1">Give Back <a class="header-anchor" href="#give-back" aria-label="Permalink to &quot;Give Back&quot;">​</a></h2><p>There are a lot of ways you can contribute to the QMK Community. The easiest way to get started is to use it and spread the word to your friends.</p><ul><li>Help people out on our forums and chat rooms: <ul><li><a href="https://www.reddit.com/r/olkb/" target="_blank" rel="noreferrer">/r/olkb</a></li><li><a href="https://discord.gg/Uq7gcHh" target="_blank" rel="noreferrer">Discord Server</a></li></ul></li><li>Contribute to our documentation by clicking &quot;Edit This Page&quot; at the bottom</li><li><a href="https://github.com/qmk/qmk_firmware/issues/new/choose" target="_blank" rel="noreferrer">Report a bug</a></li><li><a href="./contributing">Open a Pull Request</a></li></ul>', 13);
+const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="quantum-mechanical-keyboard-firmware" tabindex="-1">Quantum Mechanical Keyboard Firmware <a class="header-anchor" href="#quantum-mechanical-keyboard-firmware" aria-label="Permalink to &quot;Quantum Mechanical Keyboard Firmware&quot;">​</a></h1><h2 id="what-is-qmk-firmware" tabindex="-1">What is QMK Firmware? <a class="header-anchor" href="#what-is-qmk-firmware" aria-label="Permalink to &quot;What is QMK Firmware?&quot;">​</a></h2><p>QMK (<em>Quantum Mechanical Keyboard</em>) is an open source community centered around developing computer input devices. The community encompasses all sorts of input devices, such as keyboards, mice, and MIDI devices. A core group of collaborators maintains <a href="https://github.com/qmk/qmk_firmware" target="_blank" rel="noreferrer">QMK Firmware</a>, <a href="https://config.qmk.fm" target="_blank" rel="noreferrer">QMK Configurator</a>, <a href="https://github.com/qmk/qmk_toolbox" target="_blank" rel="noreferrer">QMK Toolbox</a>, <a href="https://qmk.fm" target="_blank" rel="noreferrer">qmk.fm</a>, and this documentation with the help of community members like you.</p><h2 id="get-started" tabindex="-1">Get Started <a class="header-anchor" href="#get-started" aria-label="Permalink to &quot;Get Started&quot;">​</a></h2><div class="tip custom-block"><p class="custom-block-title">Basic</p><p><a href="./newbs_building_firmware_configurator">QMK Configurator</a></p><p>User friendly graphical interfaces, no programming knowledge required.</p></div><div class="warning custom-block"><p class="custom-block-title">Advanced</p><p><a href="./newbs">Use The Source</a></p><p>More powerful, but harder to use.</p></div><h2 id="make-it-yours" tabindex="-1">Make It Yours <a class="header-anchor" href="#make-it-yours" aria-label="Permalink to &quot;Make It Yours&quot;">​</a></h2><p>QMK has lots of features to explore, and a good deal of reference documentation to dig through. Most features are taken advantage of by modifying your <a href="./keymap">keymap</a>, and changing the <a href="./keycodes">keycodes</a>.</p><h2 id="need-help" tabindex="-1">Need help? <a class="header-anchor" href="#need-help" aria-label="Permalink to &quot;Need help?&quot;">​</a></h2><p>Check out the <a href="./support">support page</a> to see how you can get help using QMK.</p><h2 id="give-back" tabindex="-1">Give Back <a class="header-anchor" href="#give-back" aria-label="Permalink to &quot;Give Back&quot;">​</a></h2><p>There are a lot of ways you can contribute to the QMK Community. The easiest way to get started is to use it and spread the word to your friends.</p><ul><li>Help people out on our forums and chat rooms: <ul><li><a href="https://www.reddit.com/r/olkb/" target="_blank" rel="noreferrer">/r/olkb</a></li><li><a href="https://discord.gg/qmk" target="_blank" rel="noreferrer">Discord Server</a></li></ul></li><li>Contribute to our documentation by clicking &quot;Edit This Page&quot; at the bottom</li><li><a href="https://github.com/qmk/qmk_firmware/issues/new/choose" target="_blank" rel="noreferrer">Report a bug</a></li><li><a href="./contributing">Open a Pull Request</a></li></ul>', 13);
 const _hoisted_14 = [
   _hoisted_1
 ];

assets/support.md.Bj3JfaeV.js

@@ -1,7 +1,7 @@
 import { _ as _export_sfc, c as createElementBlock, o as openBlock, a8 as createStaticVNode } from "./chunks/framework.DyMmIvSC.js";
 const __pageData = JSON.parse('{"title":"Getting Help","description":"","frontmatter":{},"headers":[],"relativePath":"support.md","filePath":"support.md"}');
 const _sfc_main = { name: "support.md" };
-const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="getting-help" tabindex="-1">Getting Help <a class="header-anchor" href="#getting-help" aria-label="Permalink to &quot;Getting Help&quot;">​</a></h1><p>There are a lot of resources for getting help with QMK.</p><p>Please read our <a href="https://qmk.fm/coc/" target="_blank" rel="noreferrer">Code of Conduct</a> before participating in any of our community spaces.</p><h2 id="realtime-chat" tabindex="-1">Realtime Chat <a class="header-anchor" href="#realtime-chat" aria-label="Permalink to &quot;Realtime Chat&quot;">​</a></h2><p>If you need help with something, the best place to get quick support is going to be on our <a href="https://discord.gg/Uq7gcHh" target="_blank" rel="noreferrer">Discord Server</a>. There is usually somebody online, and there are a bunch of very helpful people there.</p><h2 id="olkb-subreddit" tabindex="-1">OLKB Subreddit <a class="header-anchor" href="#olkb-subreddit" aria-label="Permalink to &quot;OLKB Subreddit&quot;">​</a></h2><p>The official QMK forum is <a href="https://reddit.com/r/olkb" target="_blank" rel="noreferrer">/r/olkb</a> on <a href="https://reddit.com" target="_blank" rel="noreferrer">reddit.com</a>.</p><h2 id="github-issues" tabindex="-1">GitHub Issues <a class="header-anchor" href="#github-issues" aria-label="Permalink to &quot;GitHub Issues&quot;">​</a></h2><p>You can open an <a href="https://github.com/qmk/qmk_firmware/issues" target="_blank" rel="noreferrer">issue on GitHub</a>. This is especially handy when your issue will require long-term discussion or debugging.</p>', 9);
+const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="getting-help" tabindex="-1">Getting Help <a class="header-anchor" href="#getting-help" aria-label="Permalink to &quot;Getting Help&quot;">​</a></h1><p>There are a lot of resources for getting help with QMK.</p><p>Please read our <a href="https://qmk.fm/coc/" target="_blank" rel="noreferrer">Code of Conduct</a> before participating in any of our community spaces.</p><h2 id="realtime-chat" tabindex="-1">Realtime Chat <a class="header-anchor" href="#realtime-chat" aria-label="Permalink to &quot;Realtime Chat&quot;">​</a></h2><p>If you need help with something, the best place to get quick support is going to be on our <a href="https://discord.gg/qmk" target="_blank" rel="noreferrer">Discord Server</a>. There is usually somebody online, and there are a bunch of very helpful people there.</p><h2 id="olkb-subreddit" tabindex="-1">OLKB Subreddit <a class="header-anchor" href="#olkb-subreddit" aria-label="Permalink to &quot;OLKB Subreddit&quot;">​</a></h2><p>The official QMK forum is <a href="https://reddit.com/r/olkb" target="_blank" rel="noreferrer">/r/olkb</a> on <a href="https://reddit.com" target="_blank" rel="noreferrer">reddit.com</a>.</p><h2 id="github-issues" tabindex="-1">GitHub Issues <a class="header-anchor" href="#github-issues" aria-label="Permalink to &quot;GitHub Issues&quot;">​</a></h2><p>You can open an <a href="https://github.com/qmk/qmk_firmware/issues" target="_blank" rel="noreferrer">issue on GitHub</a>. This is especially handy when your issue will require long-term discussion or debugging.</p>', 9);
 const _hoisted_10 = [
   _hoisted_1
 ];