diff options
author | Joel Challis <git@zvecr.com> | 2024-05-30 10:00:28 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-05-30 10:00:28 +0100 |
commit | b39285807e1d21300e8a5dbbf6f2c43a8aab3494 (patch) | |
tree | 311895a73c967f5d322885c1a9f1073a7b9f1b91 /docs/newbs_getting_started.md | |
parent | 6ef97172889ccd5db376b2a9f8825489e24fdac4 (diff) |
[docs] Fix code blocks overflowing page width (#23829)
Fix code blocks overflowing page width
Diffstat (limited to 'docs/newbs_getting_started.md')
-rw-r--r-- | docs/newbs_getting_started.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/newbs_getting_started.md b/docs/newbs_getting_started.md index 3a901ad7ad..9ebcccc77f 100644 --- a/docs/newbs_getting_started.md +++ b/docs/newbs_getting_started.md @@ -196,11 +196,15 @@ If you already know how to use GitHub, [we recommend that you follow these instr Now that your QMK build environment is set up, you can build a firmware for your keyboard. Start by trying to build the keyboard's default keymap. You should be able to do that with a command in this format: - qmk compile -kb <keyboard> -km default +```sh +qmk compile -kb <keyboard> -km default +``` For example, to build a firmware for a Clueboard 66% you would use: - qmk compile -kb clueboard/66/rev3 -km default +```sh +qmk compile -kb clueboard/66/rev3 -km default +``` ::: tip The keyboard option is the path relative to the keyboard directory, the above example would be found in `qmk_firmware/keyboards/clueboard/66/rev3`. If you're unsure you can view a full list of supported keyboards with `qmk list-keyboards`. |