aboutsummaryrefslogtreecommitdiff
path: root/docs/newbs_getting_started.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/newbs_getting_started.md')
-rw-r--r--docs/newbs_getting_started.md16
1 files changed, 0 insertions, 16 deletions
diff --git a/docs/newbs_getting_started.md b/docs/newbs_getting_started.md
index 5dbaa5616..d6c080173 100644
--- a/docs/newbs_getting_started.md
+++ b/docs/newbs_getting_started.md
@@ -182,22 +182,6 @@ Checking file size of clueboard_66_rev3_default.hex
182 * The firmware size is fine - 26356/28672 (2316 bytes free) 182 * The firmware size is fine - 26356/28672 (2316 bytes free)
183``` 183```
184 184
185## 5. Configure Your Build Environment (Optional)
186
187You can configure your build environment to set the defaults and make working with QMK less tedious. Let's do that now!
188
189Most people new to QMK only have 1 keyboard. You can set this keyboard as your default with the `qmk config` command. For example, to set your default keyboard to `clueboard/66/rev4`:
190
191 qmk config user.keyboard=clueboard/66/rev4
192
193You can also set your default keymap name. Most people use their GitHub username here, and we recommend that you do too.
194
195 qmk config user.keymap=<github_username>
196
197The keyboard can now be compiled without arguments using the following command after creating your keymap in the next section:
198
199 qmk compile
200
201# Creating Your Keymap 185# Creating Your Keymap
202 186
203You are now ready to create your own personal keymap! Move on to [Building Your First Firmware](newbs_building_firmware.md) for that. 187You are now ready to create your own personal keymap! Move on to [Building Your First Firmware](newbs_building_firmware.md) for that.