16 lines
3.4 KiB
JavaScript
16 lines
3.4 KiB
JavaScript
import { _ as _export_sfc, c as createElementBlock, o as openBlock, a8 as createStaticVNode } from "./chunks/framework.B9AX-CPi.js";
|
||
const __pageData = JSON.parse('{"title":"The QMK Tutorial","description":"","frontmatter":{},"headers":[],"relativePath":"newbs.md","filePath":"newbs.md","lastUpdated":null}');
|
||
const _sfc_main = { name: "newbs.md" };
|
||
const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="the-qmk-tutorial" tabindex="-1">The QMK Tutorial <a class="header-anchor" href="#the-qmk-tutorial" aria-label="Permalink to "The QMK Tutorial""></a></h1><p>Your computer keyboard has a processor inside of it, similar to the one inside your computer. This processor runs software that is responsible for detecting button presses and informing the computer when keys are pressed. QMK Firmware fills the role of that software, detecting button presses and passing that information on to the host computer. When you build your custom keymap, you are creating an executable program for your keyboard.</p><p>QMK tries to put a lot of power into your hands by making easy things easy, and hard things possible. You don't have to know how to program to create powerful keymaps — you only have to follow a few simple syntax rules.</p><p>Not sure if your keyboard can run QMK? If it's a mechanical keyboard you built yourself chances are good it can. We support a <a href="https://browse.qmk.fm/" target="_blank" rel="noreferrer">large number of hobbyist boards</a>. If your current keyboard can't run QMK there are a lot of choices out there for boards that do.</p><div class="tip custom-block"><p class="custom-block-title">Is This Guide For Me?</p><p>If the thought of programming intimidates you, please <a href="./newbs_building_firmware_configurator">take a look at our online GUI</a> instead.</p></div><h2 id="overview" tabindex="-1">Overview <a class="header-anchor" href="#overview" aria-label="Permalink to "Overview""></a></h2><p>This guide is suitable for everyone who wants to build a keyboard firmware using the source code. If you are already a programmer you will find the process very familiar and easier to follow. There are 3 main sections to this guide:</p><ol><li><a href="./newbs_getting_started">Setup Your Environment</a></li><li><a href="./newbs_building_firmware">Building Your First Firmware</a></li><li><a href="./newbs_flashing">Flashing Firmware</a></li></ol><p>This guide is focused on helping someone who has never compiled software before. It makes choices and recommendations based on that viewpoint. There are alternative methods for many of these procedures, and we support most of those alternatives. If you have any doubt about how to accomplish a task you can <a href="./support">ask us for guidance</a>.</p><h2 id="additional-resources" tabindex="-1">Additional Resources <a class="header-anchor" href="#additional-resources" aria-label="Permalink to "Additional Resources""></a></h2><p>Beyond this guide there are several resources you may find helpful while you learn QMK. We've collected them on the <a href="./syllabus">Syllabus</a> and <a href="./newbs_learn_more_resources">Learning Resources</a> pages.</p>', 11);
|
||
const _hoisted_12 = [
|
||
_hoisted_1
|
||
];
|
||
function _sfc_render(_ctx, _cache, $props, $setup, $data, $options) {
|
||
return openBlock(), createElementBlock("div", null, _hoisted_12);
|
||
}
|
||
const newbs = /* @__PURE__ */ _export_sfc(_sfc_main, [["render", _sfc_render]]);
|
||
export {
|
||
__pageData,
|
||
newbs as default
|
||
};
|