aboutsummaryrefslogtreecommitdiff
path: root/docs/newbs_building_firmware.md
diff options
context:
space:
mode:
authorskullY <skullydazed@gmail.com>2018-05-07 22:40:57 -0700
committerskullydazed <skullydazed@users.noreply.github.com>2018-05-07 22:46:26 -0700
commit303f425c6b4f9ab6056f863e515c71c9325f2bfa (patch)
tree150c9eba72bc40cf2d9a101d4a606156ea54cd0b /docs/newbs_building_firmware.md
parent9e5676650ec4ae71565201871c1aaf05e96a756b (diff)
downloadqmk_firmware-303f425c6b4f9ab6056f863e515c71c9325f2bfa.tar.gz
qmk_firmware-303f425c6b4f9ab6056f863e515c71c9325f2bfa.zip
Fix up info boxes.
Diffstat (limited to 'docs/newbs_building_firmware.md')
-rw-r--r--docs/newbs_building_firmware.md16
1 files changed, 5 insertions, 11 deletions
diff --git a/docs/newbs_building_firmware.md b/docs/newbs_building_firmware.md
index ea01a1a62..f227d623f 100644
--- a/docs/newbs_building_firmware.md
+++ b/docs/newbs_building_firmware.md
@@ -8,17 +8,15 @@ If you have closed and reopened your terminal window since following the first p
8 8
9Start by navigating to the `keymaps` folder for your keyboard. 9Start by navigating to the `keymaps` folder for your keyboard.
10 10
11{% hint style='info' %} 11?> If you are on macOS or Windows there are commands you can use to easily open the keymaps folder.
12If you are on macOS or Windows there are commands you can use to easily open the keymaps folder.
13 12
14macOS: 13?> macOS:
15 14
16 open keyboards/<keyboard_folder>/keymaps 15 open keyboards/<keyboard_folder>/keymaps
17 16
18Windows: 17?> Windows:
19 18
20 start keyboards/<keyboard_folder>/keymaps 19 start keyboards/<keyboard_folder>/keymaps
21{% endhint %}
22 20
23## Create a Copy Of The `default` Keymap 21## Create a Copy Of The `default` Keymap
24 22
@@ -32,9 +30,7 @@ Open up your `keymap.c`. Inside this file you'll find the structure that control
32 30
33This line indicates the start of the list of Layers. Below that you'll find lines containing either `LAYOUT` or `KEYMAP`, and these lines indicate the start of a layer. Below that line is the list of keys that comprise a that particular layer. 31This line indicates the start of the list of Layers. Below that you'll find lines containing either `LAYOUT` or `KEYMAP`, and these lines indicate the start of a layer. Below that line is the list of keys that comprise a that particular layer.
34 32
35{% hint style='danger' %} 33!> When editing your keymap file be careful not to add or remove any commas. If you do you will prevent your firmware from compiling and it may not be easy to figure out where the extra, or missing, comma is.
36When editing your keymap file be careful not to add or remove any commas. If you do you will prevent your firmware from compiling and it may not be easy to figure out where the extra, or missing, comma is.
37{% endhint %}
38 34
39## Customize The Layout To Your Liking 35## Customize The Layout To Your Liking
40 36
@@ -44,9 +40,7 @@ How to complete this step is entirely up to you. Make the one change that's been
44* [Features](features.md) 40* [Features](features.md)
45* [FAQ](faq.md) 41* [FAQ](faq.md)
46 42
47{% hint style='info' %} 43?> While you get a feel for how keymaps work, keep each change small. Bigger changes make it harder to debug any problems that arise.
48While you get a feel for how keymaps work, keep each change small. Bigger changes make it harder to debug any problems that arise.
49{% endhint %}
50 44
51## Build Your Firmware 45## Build Your Firmware
52 46