diff options
Diffstat (limited to 'docs')
-rw-r--r-- | docs/Macros.md | 215 | ||||
-rw-r--r-- | docs/Other-Projects.md | 62 | ||||
-rw-r--r-- | docs/SUMMARY.md | 26 | ||||
-rw-r--r-- | docs/_Sidebar.md | 21 | ||||
-rw-r--r-- | docs/_summary.md | 29 | ||||
-rw-r--r-- | docs/adding_a_keyboard_to_qmk.md | 35 | ||||
-rw-r--r-- | docs/adding_features_to_qmk.md (renamed from docs/Adding-features-to-QMK.md) | 0 | ||||
-rw-r--r-- | docs/becoming_a_qmk_collaborator.md (renamed from docs/Becoming-a-QMK-Collaborator.md) | 0 | ||||
-rw-r--r-- | docs/build_environment_setup.md (renamed from docs/Build-Environment-Setup.md) | 2 | ||||
-rw-r--r-- | docs/build_guide.md (renamed from docs/BUILD_GUIDE.md) | 2 | ||||
-rw-r--r-- | docs/build_old.md | 2 | ||||
-rw-r--r-- | docs/compatible_microcontrollers.md (renamed from docs/Compatible-Microcontrollers.md) | 0 | ||||
-rw-r--r-- | docs/custom_quantum_functions.md (renamed from docs/Custom-Quantum-Functions.md) | 20 | ||||
-rw-r--r-- | docs/cygwin_guide.md (renamed from docs/CYGWIN_GUIDE.md) | 0 | ||||
-rw-r--r-- | docs/differences_from_tmk.md (renamed from docs/Differences-from-TMK.md) | 0 | ||||
-rw-r--r-- | docs/dynamic_macros.md | 63 | ||||
-rw-r--r-- | docs/eclipse.md (renamed from docs/Eclipse.md) | 2 | ||||
-rw-r--r-- | docs/embedding.md (renamed from docs/Embedding.md) | 0 | ||||
-rw-r--r-- | docs/faq.md (renamed from docs/FAQ.md) | 0 | ||||
-rw-r--r-- | docs/faq_build.md (renamed from docs/FAQ-Build.md) | 2 | ||||
-rw-r--r-- | docs/faq_keymap.md (renamed from docs/FAQ-Keymap.md) | 21 | ||||
-rw-r--r-- | docs/fuse.txt (renamed from docs/FUSE.txt) | 0 | ||||
-rw-r--r-- | docs/git_subtree.md (renamed from docs/Git-subtree.md) | 0 | ||||
-rw-r--r-- | docs/hand_wire.md (renamed from docs/HAND_WIRE.md) | 2 | ||||
-rw-r--r-- | docs/hhkb_alt_controller.md (renamed from docs/HHKB-Alt-controller.md) | 0 | ||||
-rw-r--r-- | docs/home.md (renamed from docs/Home.md) | 67 | ||||
-rw-r--r-- | docs/key_functions.md (renamed from docs/Key-Functions.md) | 29 | ||||
-rw-r--r-- | docs/keycode.txt | 48 | ||||
-rw-r--r-- | docs/keycodes.md (renamed from docs/Keycodes.md) | 48 | ||||
-rw-r--r-- | docs/keymap.md (renamed from docs/Keymap.md) | 0 | ||||
-rw-r--r-- | docs/keymap_examples.md (renamed from docs/Keymap-examples.md) | 0 | ||||
-rw-r--r-- | docs/kiibohd.asciidoc (renamed from docs/Kiibohd.asciidoc) | 0 | ||||
-rw-r--r-- | docs/leader_key.md (renamed from docs/Leader-Key.md) | 0 | ||||
-rw-r--r-- | docs/license_clarification.md (renamed from docs/License-Clarification.md) | 0 | ||||
-rw-r--r-- | docs/license_clarification_details.md (renamed from docs/License-Clarification-Details.md) | 0 | ||||
-rw-r--r-- | docs/macros.md | 158 | ||||
-rw-r--r-- | docs/make_instructions.md (renamed from docs/Make-Instructions.md) | 2 | ||||
-rw-r--r-- | docs/mbed_cortex_porting.md (renamed from docs/mbed-cortex-porting.md) | 0 | ||||
-rw-r--r-- | docs/memory_write_error,_use_debug_for_more_info.md (renamed from docs/Memory-write-error,-use-debug-for-more-info.md) | 0 | ||||
-rw-r--r-- | docs/modding_your_keyboard.md (renamed from docs/Modding-your-keyboard.md) | 25 | ||||
-rw-r--r-- | docs/mouse_keys.md (renamed from docs/Mouse-keys.md) | 0 | ||||
-rw-r--r-- | docs/pcb_guide.md (renamed from docs/PCB_GUIDE.md) | 2 | ||||
-rw-r--r-- | docs/porting_your_keyboard_to_qmk.md (renamed from docs/Porting-your-keyboard-to-QMK.md) | 6 | ||||
-rw-r--r-- | docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md (renamed from docs/Porting-Your-Keyboard-to-QMK-(ARM-and-other-ChibiOS-CPUs).md) | 0 | ||||
-rw-r--r-- | docs/power.txt (renamed from docs/POWER.txt) | 0 | ||||
-rw-r--r-- | docs/previously_asked_questions.asciidoc (renamed from docs/Previously-Asked-Questions.asciidoc) | 0 | ||||
-rw-r--r-- | docs/qmk_overview.md (renamed from docs/QMK-Overview.md) | 2 | ||||
-rw-r--r-- | docs/report_descriptor.md (renamed from docs/Report-Descriptor.md) | 0 | ||||
-rw-r--r-- | docs/space_cadet_shift.md (renamed from docs/Space-Cadet-Shift.md) | 0 | ||||
-rw-r--r-- | docs/tap_dance.md (renamed from docs/Tap-Dance.md) | 0 | ||||
-rw-r--r-- | docs/test_for_asciidoc.asciidoc (renamed from docs/Test-for-ASCIIDOC.asciidoc) | 0 | ||||
-rw-r--r-- | docs/tmk_based_projects.md (renamed from docs/TMK-Based-Projects.md) | 0 | ||||
-rw-r--r-- | docs/tmk_own_projects.md (renamed from docs/TMK-Own-Projects.md) | 0 | ||||
-rw-r--r-- | docs/tmk_readme.md (renamed from docs/TMK_README.md) | 8 | ||||
-rw-r--r-- | docs/unicode_and_additional_language_support.md (renamed from docs/Unicode-and-additional-language-support.md) | 0 | ||||
-rw-r--r-- | docs/unit_testing.md (renamed from docs/Unit-testing.md) | 0 | ||||
-rw-r--r-- | docs/usb_hid.md (renamed from docs/USB-HID.md) | 0 | ||||
-rw-r--r-- | docs/usb_nkro.txt (renamed from docs/USB_NKRO.txt) | 0 | ||||
-rw-r--r-- | docs/vagrant_guide.md (renamed from docs/VAGRANT_GUIDE.md) | 4 |
59 files changed, 436 insertions, 467 deletions
diff --git a/docs/Macros.md b/docs/Macros.md deleted file mode 100644 index 994d01928f..0000000000 --- a/docs/Macros.md +++ /dev/null @@ -1,215 +0,0 @@ -# Macro shortcuts: Send a whole string when pressing just one key - -Instead of using the `ACTION_MACRO` function, you can simply use `M(n)` to access macro *n* - *n* will get passed into the `action_get_macro` as the `id`, and you can use a switch statement to trigger it. This gets called on the keydown and keyup, so you'll need to use an if statement testing `record->event.pressed` (see keymap_default.c). - -```c -const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) // this is the function signature -- just copy/paste it into your keymap file as it is. -{ - switch(id) { - case 0: // this would trigger when you hit a key mapped as M(0) - if (record->event.pressed) { - return MACRO( I(255), T(H), T(E), T(L), T(L), W(255), T(O), END ); // this sends the string 'hello' when the macro executes - } - break; - } - return MACRO_NONE; -}; -``` -A macro can include the following commands: - -* I() change interval of stroke in milliseconds. -* D() press key. -* U() release key. -* T() type key(press and release). -* W() wait (milliseconds). -* END end mark. - -So above you can see the stroke interval changed to 255ms between each keystroke, then a bunch of keys being typed, waits a while, then the macro ends. - -Note: Using macros to have your keyboard send passwords for you is possible, but a bad idea. - -## Advanced macro functions - -To get more control over the keys/actions your keyboard takes, the following functions are available to you in the `action_get_macro` function block: - -* `record->event.pressed` - -This is a boolean value that can be tested to see if the switch is being pressed or released. An example of this is - -```c -if (record->event.pressed) { - // on keydown -} else { - // on keyup -} -``` - -* `register_code(<kc>);` - -This sends the `<kc>` keydown event to the computer. Some examples would be `KC_ESC`, `KC_C`, `KC_4`, and even modifiers such as `KC_LSFT` and `KC_LGUI`. - -* `unregister_code(<kc>);` - -Parallel to `register_code` function, this sends the `<kc>` keyup event to the computer. If you don't use this, the key will be held down until it's sent. - -* `layer_on(<n>);` - -This will turn on the layer `<n>` - the higher layer number will always take priority. Make sure you have `KC_TRNS` for the key you're pressing on the layer you're switching to, or you'll get stick there unless you have another plan. - -* `layer_off(<n>);` - -This will turn off the layer `<n>`. - -* `clear_keyboard();` - -This will clear all mods and keys currently pressed. - -* `clear_mods();` - -This will clear all mods currently pressed. - -* `clear_keyboard_but_mods();` - -This will clear all keys besides the mods currently pressed. - -* `update_tri_layer(layer_1, layer_2, layer_3);` - -If the user attempts to activate layer 1 AND layer 2 at the same time (for example, by hitting their respective layer keys), layer 3 will be activated. Layers 1 and 2 will _also_ be activated, for the purposes of fallbacks (so a given key will fall back from 3 to 2, to 1 -- and only then to 0). - -### Naming your macros - -If you have a bunch of macros you want to refer to from your keymap, while keeping the keymap easily readable, you can just name them like so: - -``` -#define AUD_OFF M(6) -#define AUD_ON M(7) -#define MUS_OFF M(8) -#define MUS_ON M(9) -#define VC_IN M(10) -#define VC_DE M(11) -#define PLOVER M(12) -#define EXT_PLV M(13) -``` - -As was done on the [Planck default keymap](https://github.com/qmk/qmk_firmware/blob/master/keyboards/planck/keymaps/default/keymap.c#L33-L40) - -#### Timer functionality - -It's possible to start timers and read values for time-specific events - here's an example: - -```c -static uint16_t key_timer; -key_timer = timer_read(); -if (timer_elapsed(key_timer) < 100) { - // do something if less than 100ms have passed -} else { - // do something if 100ms or more have passed -} -``` - -It's best to declare the `static uint16_t key_timer;` outside of the macro block (top of file, etc). - -### Example: Single-key copy/paste (hold to copy, tap to paste) - -With QMK, it's easy to make one key do two things, as long as one of those things is being a modifier. :) So if you want a key to act as Ctrl when held and send the letter R when tapped, that's easy: `CTL_T(KC_R)`. But what do you do when you want that key to send Ctrl-V (paste) when tapped, and Ctrl-C (copy) when held? - -Here's what you do: - - -``` -static uint16_t key_timer; - -const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) -{ - switch(id) { - case 0: { - if (record->event.pressed) { - key_timer = timer_read(); // if the key is being pressed, we start the timer. - } - else { // this means the key was just released, so we can figure out how long it was pressed for (tap or "held down"). - if (timer_elapsed(key_timer) > 150) { // 150 being 150ms, the threshhold we pick for counting something as a tap. - return MACRO( D(LCTL), T(C), U(LCTL), END ); - } - else { - return MACRO( D(LCTL), T(V), U(LCTL), END ); - } - } - break; - } - } - return MACRO_NONE; -}; -``` - -And then, to assign this macro to a key on your keyboard layout, you just use `M(0)` on the key you want to press for copy/paste. - -# Dynamic macros: record and replay macros in runtime - -In addition to the static macros described above, you may enable the dynamic macros which you may record while writing. They are forgotten as soon as the keyboard is unplugged. Only two such macros may be stored at the same time, with the total length of 64 keypresses (by default). - -To enable them, first add a new element to the `planck_keycodes` enum — `DYNAMIC_MACRO_RANGE`: - - enum planck_keycodes { - QWERTY = SAFE_RANGE, - COLEMAK, - DVORAK, - PLOVER, - LOWER, - RAISE, - BACKLIT, - EXT_PLV, - DYNAMIC_MACRO_RANGE, - }; - -It must be the last element because `dynamic_macros.h` will add some more keycodes after it. - -Below it include the `dynamic_macro.h` header: - - #include "dynamic_macro.h"` - -Add the following keys to your keymap: - -- `DYN_REC_START1` — start recording the macro 1, -- `DYN_REC_START2` — start recording the macro 2, -- `DYN_MACRO_PLAY1` — replay the macro 1, -- `DYN_MACRO_PLAY2` — replay the macro 2, -- `DYN_REC_STOP` — finish the macro that is currently being recorded. - -Add the following code to the very beginning of your `process_record_user()` function: - - if (!process_record_dynamic_macro(keycode, record)) { - return false; - } - -That should be everything necessary. To start recording the macro, press either `DYN_REC_START1` or `DYN_REC_START2`. To finish the recording, press the `DYN_REC_STOP` layer button. To replay the macro, press either `DYN_MACRO_PLAY1` or `DYN_MACRO_PLAY2`. - -Note that it's possible to replay a macro as part of a macro. It's ok to replay macro 2 while recording macro 1 and vice versa but never create recursive macros i.e. macro 1 that replays macro 1. If you do so and the keyboard will get unresponsive, unplug the keyboard and plug it again. - -For users of the earlier versions of dynamic macros: It is still possible to finish the macro recording using just the layer modifier used to access the dynamic macro keys, without a dedicated `DYN_REC_STOP` key. If you want this behavior back, use the following snippet instead of the one above: - - uint16_t macro_kc = (keycode == MO(_DYN) ? DYN_REC_STOP : keycode); - if (!process_record_dynamic_macro(macro_kc, record)) { - return false; - } - -If the LED-s 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 setting the `DYNAMIC_MACRO_SIZE` preprocessor macro (default value: 128; please read the comments for it in the header). - -For the details about the internals of the dynamic macros, please read the comments in the `dynamic_macro.h` header. - -# Sending strings -Some people want to have a password or some text on a key. This is possible without having to do every key individually using `SEND_STRING("<text>");`. Note the caps, because `send_string("<text>");` does something else. For example: -```c -const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) // this is the function signature -- just copy/paste it into your keymap file as it is. -{ - switch(id) { - case 0: // this would trigger when you hit a key mapped as M(0) - if (record->event.pressed) { - SEND_STRING("QMK is the best thing ever!"); // This would type "QMK is the best thing ever!" (without quotation marks). - return false; // This is false because it has to return something. - } - break; - } - return MACRO_NONE; -}; -``` -If you'd want it to press enter as well, just replace `return false;` with `return MACRO( T(ENT), END );`. diff --git a/docs/Other-Projects.md b/docs/Other-Projects.md deleted file mode 100644 index 163c7c1cf4..0000000000 --- a/docs/Other-Projects.md +++ /dev/null @@ -1,62 +0,0 @@ -Keyboard Firmware Projects other than TMK -================================ -## PJRC USB Keyboard/Mouse Example[USB][PJRC][Teensy][AVR] -- <http://www.pjrc.com/teensy/usb_keyboard.html> -- <http://www.pjrc.com/teensy/usb_mouse.html> - -## kbupgrade[USB][V-USB][AVR] -- <http://github.com/rhomann/kbupgrade> -- <http://geekhack.org/showwiki.php?title=Island:8406> - -## c64key[USB][V-USB][AVR] -- <http://symlink.dk/projects/c64key/> - -## rump[USB][V-USB][AVR] -- <http://mg8.org/rump/> -- <http://github.com/clee/rump> - -## dulcimer[USB][V-USB][AVR] -- <http://www.schatenseite.de/dulcimer.html> - -## humblehacker-keyboard[USB][LUFA][AVR][Ergo] -- <http://github.com/humblehacker> -- <http://www.humblehacker.com/keyboard/> -- <http://geekhack.org/showwiki.php?title=Island:6292> - -## ps2avr[PS/2][AVR] -- <http://sourceforge.net/projects/ps2avr/> - -## ErgoDox[Ergo][Split][USB][AVR] -- <http://geekhack.org/index.php?topic=22780.0> -- <https://github.com/benblazak/ergodox-firmware> -- <https://github.com/cub-uanic/tmk_keyboard> - -## Suka's keyboard collection[Ergo][Split][3DPrinting][USB][AVR] -- <http://deskthority.net/workshop-f7/my-diy-keyboard-collection-or-how-i-became-a-kb-geek-t2534.html> -- <https://github.com/frobiac/adnw> - -## bpiphany's AVR-Keyboard[PJRC][AVR][USB] -- <https://github.com/BathroomEpiphanies/AVR-Keyboard> -- <http://deskthority.net/wiki/HID_Liberation_Device_-_DIY_Instructions> -- <http://deskthority.net/wiki/Phantom> - -## USB-USB keyboard remapper[converter][USB-USB][AVR][Arduino] -- <http://forum.colemak.com/viewtopic.php?pid=10837> -- <https://github.com/darkytoothpaste/keymapper> - -## USB-USB converter threads[converter][USB-USB] -- <http://deskthority.net/workshop-f7/is-remapping-a-usb-keyboard-using-teensy-possible-t2841-30.html> -- <http://geekhack.org/index.php?topic=19458.0> - -## kbdbabel.org[converter][vintage][protocol][8051] -Great resource of vintage keyboard protocol information and code - -- <http://www.kbdbabel.org/> - -## Haata's kiibohd Controller[converter][vintage][protocol][AVR][PJRC][Cortex] -A lots of vintage keyboard protocol supports - -- <https://github.com/kiibohd/controller> - -## Kinesis ergonomic keyboard firmware replacement[V-USB][LUFA][Ergo] -- <https://github.com/chrisandreae/kinesis-firmware> diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md deleted file mode 100644 index 99845a7b68..0000000000 --- a/docs/SUMMARY.md +++ /dev/null @@ -1,26 +0,0 @@ - -### Getting started -* [Introduction](/Home.md) -* [QMK Overview](/QMK-Overview.md) -* [Build Environment Setup](/Build-Environment-Setup.md) - -### Making a keymap -* [Keymap overview](/Keymap.md) -* [Keycodes](/Keycodes.md) -* [Layer switching](/Key-Functions.md) -* [Leader Key](/Leader-Key.md) -* [Macros](/Macros.md) -* [Space Cadet](/Space-Cadet-Shift.md) -* [Tap Dance](/Tap-Dance.md) -* [Mouse keys](/Mouse-keys.md) -* [FAQ: Creating a Keymap](/FAQ-Keymap.md) -* [FAQ: Compiling QMK](/FAQ-Build.md) - -### For hardware makers and modders -* [Modding your keyboard](/Modding-your-keyboard.md) -* [Porting your keyboard to QMK](/Porting-your-keyboard-to-QMK.md) -* [Adding features to QMK](/Adding-features-to-QMK.md) - -### Other topics -* [General FAQ](/FAQ.md) -* [Differences from TMK](/Differences-from-TMK.md) diff --git a/docs/_Sidebar.md b/docs/_Sidebar.md deleted file mode 100644 index f82c44c3eb..0000000000 --- a/docs/_Sidebar.md +++ /dev/null @@ -1,21 +0,0 @@ -* [Wiki Home](/qmk/qmk_firmware/wiki) -* Getting started - * [QMK Overview](QMK-Overview) - * [Build Environment Setup](Build-Environment-Setup) -* [Overview for keymap creators](Keymap) - * [Keycodes](Keycodes) - * [Layer switching](Key-Functions) - * [Leader Key](Leader-Key) - * [Macros](Macros) - * [Space Cadet](Space-Cadet-Shift) - * [Tap Dance](Tap-Dance) - * [Mouse keys](Mouse-keys) - * [FAQ: Creating a Keymap](FAQ-Keymap) - * [FAQ: Compiling QMK](FAQ-Build) -* For hardware makers and modders - * [Modding your keyboard](Modding-your-keyboard) - * [Porting your keyboard to QMK](Porting-your-keyboard-to-QMK) - * [Adding features to QMK](Adding-features-to-QMK) -* [General FAQ](FAQ) - - diff --git a/docs/_summary.md b/docs/_summary.md new file mode 100644 index 0000000000..23128cafe4 --- /dev/null +++ b/docs/_summary.md @@ -0,0 +1,29 @@ + +### Getting started +* [Introduction](home.md) +* [QMK Overview](qmk_overview.md) +* [Build Environment Setup](build_environment_setup.md) + +### Making a keymap +* [Keymap overview](keymap.md) +* [Custom Quantum Functions](custom_quantum_functions.md) +* [Keycodes](keycodes.md) +* [Layer switching](key_functions.md) +* [Leader Key](leader_key.md) +* [Macros](macros.md) +* [Dynamic Macros](dynamic_macros.md) +* [Space Cadet](space_cadet_shift.md) +* [Tap Dance](tap_dance.md) +* [Mouse keys](mouse_keys.md) +* [FAQ: Creating a Keymap](faq_keymap.md) +* [FAQ: Compiling QMK](faq_build.md) + +### For hardware makers and modders +* [Adding a keyboard to QMK](adding_a_keyboard_to_qmk.md) +* [Porting your keyboard to QMK](porting_your_keyboard_to_qmk.md) +* [Modding your keyboard](modding_your_keyboard.md) +* [Adding features to QMK](adding_features_to_qmk.md) + +### Other topics +* [General FAQ](faq.md) +* [Differences from TMK](differences_from_tmk.md) diff --git a/docs/adding_a_keyboard_to_qmk.md b/docs/adding_a_keyboard_to_qmk.md new file mode 100644 index 0000000000..51c4c44109 --- /dev/null +++ b/docs/adding_a_keyboard_to_qmk.md @@ -0,0 +1,35 @@ +# Adding your keyboard to QMK + +We welcome all keyboard projects into QMK, but ask that you try to stick to a couple guidelines that help us keep things organised and consistent. + +## Naming your directory/project + +All names should be lowercase alphanumeric, and separated by an underscore (`_`), but not begin with one. Dashes (`-`) aren't allow by our build system, and will confuse it with keymaps/subprojects. Your directory and your `.h` and `.c` files should have exactly the same name. Subprojects/revision should follow the same format. + +## `readme.md` + +All projects need to have a `readme.md` file that explains what the keyboard is, who made it, where it is available, and links to move information (template coming). + +## Image/Hardware files + +In an effort to keep the repo size down, we're no longer accepting images of any format in the repo, with few exceptions. Hosting them elsewhere (imgur) and linking them in the readme.md is the preferred method. + +Any sort of hardware file (plate, case, pcb) can't be stored in qmk_firmware, but we have the [qmk.fm repo](https://github.com/qmk/qmk.fm) where such files (as well as in-depth info) can be store, and viewed on [qmk.fm](http://qmk.fm). Downloadable files are stored in `/<keyboard>/` (name follows the same format as above) which are served at `http://qmk.fm/<keyboard>/`, and pages are generated from `/_pages/<keyboard>/` which are served at the same location (.md files are generated into .html files through Jekyll). Check out the `lets_split` directory for an example. + +## Non-production/handwired projects + +We're happy to accept any project that uses QMK, including prototypes and handwired ones, but we have a separate `/keyboards/handwired/` folder for them, so the main `/keyboards/` folder doesn't get overcrowded. If a prototype project becomes a production project at some point in the future, we'd be happy to move it to the main `/keyboards/` folder! + +## Warnings as errors + +When developing your keyboard, keep in mind that all warnings will be treated as errors - these small warnings can build-up and cause larger errors down the road (and keeping them is generally a bad practice). + +## Licenses + +If you're adapting your keyboard's setup from another project, but not using the same code, but sure to update the copyright header at the top of the files to show your name, it this format: + + Copyright 2017 Your Name <your@email.com> + +## Technical details + +If you're looking for more information on making your keyboard work with QMK, [check out this guide](porting_your_keyboard_to_qmk.md)! diff --git a/docs/Adding-features-to-QMK.md b/docs/adding_features_to_qmk.md index f6f7cba208..f6f7cba208 100644 --- a/docs/Adding-features-to-QMK.md +++ b/docs/adding_features_to_qmk.md diff --git a/docs/Becoming-a-QMK-Collaborator.md b/docs/becoming_a_qmk_collaborator.md index 1427675fdd..1427675fdd 100644 --- a/docs/Becoming-a-QMK-Collaborator.md +++ b/docs/becoming_a_qmk_collaborator.md diff --git a/docs/Build-Environment-Setup.md b/docs/build_environment_setup.md index d4cec91c7b..442038a58d 100644 --- a/docs/Build-Environment-Setup.md +++ b/docs/build_environment_setup.md @@ -110,7 +110,7 @@ docker run -e keymap=default -e subproject=ez -e keyboard=ergobox --rm -v D:/Use This will compile the targeted keyboard/keymap and leave it in your QMK directory for you to flash. ### Vagrant -If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](https://github.com/qmk/qmk_firmware/blob/master/doc/VAGRANT_GUIDE.md). +If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [vagrant guide](vagrant_guide.md). ## Verify Your Installation 1. If you haven't already, obtain this repository ([https://github.com/qmk/qmk_firmware](https://github.com/qmk/qmk_firmware)). You can either download it as a zip file and extract it, or clone it using the command line tool git or the Github Desktop application. diff --git a/docs/BUILD_GUIDE.md b/docs/build_guide.md index 78cf00b917..8573b0fd15 100644 --- a/docs/BUILD_GUIDE.md +++ b/docs/build_guide.md @@ -35,7 +35,7 @@ Debian/Ubuntu example: sudo apt-get install gcc-avr avr-libc dfu-programmer ### Vagrant -If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](VAGRANT_GUIDE.md). +If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [vagrant guide](vagrant_guide.md). ## Verify Your Installation 1. If you haven't already, obtain this repository ([https://github.com/qmk/qmk_firmware](https://github.com/qmk/qmk_firmware)). You can either download it as a zip file and extract it, or clone it using the command line tool git or the Github Desktop application. diff --git a/docs/build_old.md b/docs/build_old.md index 5c2d57d02d..9ae3a64ae4 100644 --- a/docs/build_old.md +++ b/docs/build_old.md @@ -1,7 +1,7 @@ Build Firmware and Program Controller ===================================== -## This guide may be out-dated - use doc/BUILD_GUIDE.md instead +## This guide may be out-dated - use [build_guide.md](build_guide.md) instead Download and Install -------------------- diff --git a/docs/Compatible-Microcontrollers.md b/docs/compatible_microcontrollers.md index 20ba620f6d..20ba620f6d 100644 --- a/docs/Compatible-Microcontrollers.md +++ b/docs/compatible_microcontrollers.md diff --git a/docs/Custom-Quantum-Functions.md b/docs/custom_quantum_functions.md index 1c4929e5a8..0fb1c163b7 100644 --- a/docs/Custom-Quantum-Functions.md +++ b/docs/custom_quantum_functions.md @@ -4,7 +4,7 @@ A custom keyboard is about more than sending button presses to your computer. QM We have structured QMK as a hierarchy: -* Core +* Core (`_quantum`) * Keyboard/Revision (`_kb`) * Keymap (`_user`) |