typos and spelling.

This commit is contained in:
Gabe Venberg 2024-07-29 17:57:54 -05:00
parent fb44be7ee5
commit 3d4349710b
8 changed files with 48 additions and 47 deletions

View file

@ -6,9 +6,9 @@ draft = false
image = "keyboard_with_case"
+++
Ive been using a split keyboard at home now for several years
I've been using a split keyboard at home now for several years
(specifically, the [UHKv2](https://ultimatehackingkeyboard.com/), though nowadays I probably would have gone for something ortholinear)
and ive always wanted one for the office.
and I've always wanted one for the office.
The problem was, if I was going to get a new keyboard,
I wanted it to be for both the office and travel,
and most prebuilts around are not that portable.
@ -25,13 +25,13 @@ and started the long wait for it all to arrive.
In the meantime, I researched how to flash the [elite-pi](https://docs.keeb.io/elite-pi-guide)'s I had purchased with QMK.
(Normal elite-c's were out of stock, and I like the RP2040.)
Its a little bit different, but as long as you have used QMK before, it isnt much extra.
Its a little bit different, but as long as you have used QMK before, it isn't much extra.
When the parts came,
I socketed the microcontrollers,
soldered the sockets to the pcbs,
and finally soldered the switches in.
(I used choc purpz, a bit of a leap of faith from my usual heavy tactile switches).
(I used choc Purpz, a bit of a leap of faith from my usual heavy tactile switches).
I did ruin one switch by letting a leg getting hot enough to melt the housing plastic,
and desoldering it was unexpectedly difficult,
but not every build can be mistake free, right?
@ -42,11 +42,11 @@ Flashing QMK was uneventful, working exactly as the [QMK docs](https://github.co
I would, however, recommend flashing the micros *before* doing any soldering,
I had to take my micros out of their sockets in order to access the boot buttons.
(once the keyboard is assembled, there is a dedicated keycombo on most layouts to enter the bootloader,
so you dont have to do this every time you reflash your keyboard)
so you don't have to do this every time you reflash your keyboard)
## Layout
I wasnt feeling quite adventurous enough to switch away from qwerty,
I was'nt feeling quite adventurous enough to switch away from qwerty,
but, the Sweep being a 34-key board, some layout adjustment would be needed.
I took the Sweeps [default layout](https://github.com/qmk/qmk_firmware/tree/master/keyboards/ferris/keymaps/default)
and used the [QMK configurator](https://config.qmk.fm/) to customize it.
@ -83,9 +83,9 @@ but I am now at the point where it feels natural to type on.
I want this keyboard to be both my work keyboard as well as my travel keyboard,
so a case is essential.
(I dont want to carelessly set it down on a conductive surface and fry the micros, for example)
(I don't want to carelessly set it down on a conductive surface and fry the micros, for example)
I asked a friend to print [this case](https://www.printables.com/model/513831-ferris-sweep-22-case) for me.
(I didnt have any TPU on hand.)
(I didn't have any TPU on hand.)
With the case and some rubber feet to keep it from sliding over the surface,
it becomes a very serviceable little travel keyboard,
one I can throw in my laptop bag and use in place of the built-in keyboard.
@ -106,6 +106,6 @@ and if they do, I did socket the microcontrollers for easy replacement.
It took me all of a week to fall in love with the sweeps form factor,
and, 1 month later, Im convinced I will never let myself work on a regular keyboard for a long period of time again,
thats how much Ive come to appreciate split keyboards.
that's how much Ive come to appreciate split keyboards.
The fact that the board has no pesky diodes or other surface mount parts means its very accessible first build,
and one Id recommend to anyone interested in improving their typing ergonomics.