Skip to content

Commit 34ea6ff

Browse files
authored
Merge pull request #13 from kdb424/topic-ZMK
feat: ZMK GUI guide
2 parents 69d88ba + a506798 commit 34ea6ff

File tree

1 file changed

+81
-0
lines changed

1 file changed

+81
-0
lines changed

guides/zmkGui.md

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
title: ZMK GUI
3+
description: How to use a GUI to configure your ZMK powered keyboard.
4+
author: Boardsource
5+
subcategory: easy
6+
draft: false
7+
tags:
8+
- zmk
9+
- flashing
10+
banner: https://boardsource.imgix.net/3f11ba0e-4a8f-4dd6-894d-4e275a073c4c.jpg
11+
thumbnail: https://boardsource.imgix.net/f2a7c864-074e-406f-9c23-1d26813114e4.jpg?auto=format&ixlib=react-9.2.0&q=80&w=200&dpr=1
12+
---
13+
14+
# Getting started with ZMK on a GUI!
15+
16+
One of the big put off's for people with ZMK has been the lack of GUI tools and
17+
editing the keymap by hand. That's no longer the case thanks to
18+
[Nick](https://github.com/nickcoutsos), one of the amazing community members.
19+
This will work with any keyboard that ZMK supports, and we are making it even
20+
easier to get up and running to start editing with their keymap editor on a
21+
brand new board!
22+
23+
# Step 1: Pick your keyboard
24+
25+
We have made templates for our boards that support ZMK to make this easy for
26+
anyone without the need to ever open the command line. Just select your keyboard
27+
from the table below, and make sure you pick the controller that matches what's
28+
in your keyboard. For example the nice!nano (or SuperMini uses the nice!nano),
29+
or integrated if there is no controller that a user solders to the board.
30+
31+
| Nice!Nano/SuperMini | Blok | Integrated |
32+
|---------------------------------------------------------------------------|------|------------|
33+
| [Corne](https://github.com/boardsource/zmk-config_corne_nnv2) | | |
34+
| [Lily58/Lulu](https://github.com/boardsource/zmk-config_lily58_nnv2) | | |
35+
| [Microdox v2](https://github.com/boardsource/zmk-config_microdoxv2_nnv2) | | |
36+
| [Sweep](https://github.com/boardsource/zmk-config_sweep_nnv2) | | |
37+
| [TG4X](https://github.com/boardsource/zmk-config_tg4x_nnv2) | | |
38+
| [3x4 Macropad](https://github.com/boardsource/zmk-config_3x4_nnv2) | | |
39+
| [Sofle](https://github.com/boardsource/zmk-config_sofle_nnv2) | | |
40+
41+
# Step 2: Create a reposity from the template.
42+
43+
You will need a GitHub account for this. If you don't have one, take a moment
44+
now to create one. Not only does this make working with ZMK easier, it means
45+
that your keymaps are always backed up and ready for you anywhere in the world!
46+
Once you have an account, and are logged in, you'll create a repository for your
47+
keyboard like this. Make sure to name the repository something you'll remember.
48+
Many people use `zmk-keyboardNameHere`
49+
50+
![](https://images.boardsource.xyz/template%20how%20to.png)
51+
52+
# Step 3: Connect the GUI tool to the reposity you created
53+
54+
At this point, we are almost there! We'll want to go to [the keymap
55+
editor](https://nickcoutsos.github.io/keymap-editor/) and follow the
56+
instructions given. It will want you to connect your code from GitHub to the
57+
tool so it can access and edit your keymap all in the tool.
58+
59+
# Step 4: Getting the files for your keyboard
60+
61+
![](https://images.boardsource.xyz/signal-2023-10-20-120918_002.png)
62+
63+
![](https://images.boardsource.xyz/signal-2023-10-20-120918_003.png)
64+
65+
We have everything we want, and just have to put it on the keyboard.
66+
In the editor, there's a save icon at the top. Make sure to hit that, and then
67+
the button to the right. That will take you back to GitHub to get your firmware,
68+
built automatically for you! If you see a yellow spinning icon or text like `0/2
69+
jobs completed`, just wait a moment while it does the compiling for you. It may
70+
take just a minute or two. Once it's all green, you'll see a file in the
71+
Artifacts section called `firmware.zip`. Click that and download it. That will
72+
be your firmware ready to go for your board! Make sure to extract the zip into
73+
UF2 files. Split keyboards get 2 firmware. One for left, and one for right.
74+
Make sure to not mix them up.
75+
76+
# Step 5: Flashing
77+
78+
This is the normal process for flashing your controller. With most controllers,
79+
you can double tap reset, and you'll have a "flash drive" show up on your
80+
system. You simply drop the UF2 file onto it, and it will flash and
81+
automatically reboot, ready to go as a keyboard.

0 commit comments

Comments
 (0)