keyboard

KO | EN

gitlite — search

#python #ai #typescript #go #rust #linux #awesome #cli #awesome-list #security #pytorch #mcp #openai #open-source

(★ 14)

An efficient 40% keyboard layout

keyboard 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# An efficient 40% keyboard layout

This essay summarizes my process of designing an “optimal” keyboard layout. You can view the layout layer by layer at [QMK configurator](https://config.qmk.fm/#/) by uploading one of the [JSON files](https://github.com/EdvardSire/keyboard/blob/master/niu_mini_layout_planck_mit_mine_clean.json). If you are just interested in the finished layout, feel free to skip to [The final layout](https://github.com/EdvardSire/keyboard#the-final-layout).

- [Why 40%](https://github.com/EdvardSire/keyboard#why-40%)
- [Motivation](https://github.com/EdvardSire/keyboard#motivation)
- [Reducing capitalization to one key](https://github.com/EdvardSire/keyboard#reducing-capitalization-to-one-key)
- [The power of QMK](https://github.com/EdvardSire/keyboard#the-power-of-qmk)
- [Numbers without a number row](https://github.com/EdvardSire/keyboard#numbers-without-a-number-row)
- [Special characters](https://github.com/EdvardSire/keyboard#special-characters)
- [Making the keyboard complete](https://github.com/EdvardSire/keyboard#making-the-keyboard-complete)
- [The final layout](https://github.com/EdvardSire/keyboard#the-final-layout)

## Why 40%?
When I was searching for a new keyboard back in 2019 I realised that I was looking for the smallest possible, yet _efficient_, keyboard.
I wanted an ortholinear keyboard since it minimizes the keyboard footprint,
but you can argue that keyboard size is more accurately defined by the number of keys.
Anyways, I concluded that a 40%, more specifically a 4x12, is the smallest keyboard that meets the following requirements:

- QWERTY on a 3x10 grid
- ESC and TAB on the left
- Backspace on the right
- The CTRL, Super, Alt and Spacebar on the bottom

![Initial keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-initial.png)

## Motivation
The purpose of the layout is to combine a small footprint with an efficient layout.
A 4x12 footprint means that the fingers can stay on the home row.
This is intrinsically efficient but has to be combined with a sensible layout that doesn’t restrict typing speed or usability.

## Reducing capitalization to one key
I think anyone coming from a keyboard with 68 keys or more would naturally place Right and Left Shift under TAB and apostrophe ('), and Capslock somewhere on the bottom row.
I think that having three keys for capitalization is ludicrous.
In addition to the fact that when your “home row pinkies” press Shift, like in the image below, you can no longer press Q, A, Z, or P with their dedicated fingers.
One could argue that this quirk of Shift placement doesn’t necessarily affect typing speed, but I fundamentally dislike it and believe that capitalization should be done differently.

![Shiftkey homerow](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-shiftkey-homerow.png)

Why two Shift keys in the first place? I’d argue that it stems from the capitalization problem of A, Q, Z, and P.
This is (I guess) also the reason why we have Caps Lock, since holding down Right or Left Shift permanently isn't feasible.

Okay, so how do we improve this? The reason for multiple Shift keys is that the home row pinkies can’t be held down permanently, this is what creates the need for Caps Lock.
That means that if we solve Shift keys we don’t need Caps Lock.
And the problem with Shift keys is that their fingers, the pinkies, are needed for other important keys.
In fact, it doesn’t make sense to use **any** of the home row fingers for capitalization, because they press the letters to capitalize.
That’s why using the non-Spacebar-thumb for Shift magically reduces capitalization to one key, since it can be held down permanently.

![Shift keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-shift.png)

## The power of QMK
At this point it might seem like the layout is running out of keys, yes, but actually no.
[QMK](https://qmk.fm) is a powerful keyboard firmware tool that allows for arbitrary layers.
If you have every used the FN-key this concept is familiar.
But doing this for any type if key allows for complex and powerful keyboard layouts.
I'd recommend checking out all the built in features at [QMK config](https://config.qmk.fm).

## Numbers without a number row
IMHO the numpad is just superior.
It felt very natural to place the numbers on a dedicated layer.
Simply press "left shift" to change the keys under the right hand to a numpad.
They ended up on the right "under" the home row.
This is both convenient and fast since the fingers doesn't have to move.

![Numbers keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-numbers-initial.png)

![Numbtheme No, but trust me you will never ever have to do that. The battery, once charged, works for so long. rs-layer keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-numbers-layer.png)

## Special characters
Special characters are usually mapped to the number row, so it's natural to dedicate a new layer.
They can be placed on the same layers as the numbers, but this is unintuitive and unnecesassry.
As you can see in the image below most of the special characters are where they would be on a QWERTY layout.
But since the keyboard is only 12 keys wide I had to make some adjustments.

- Prioritized (~)-($), deprioritized (%), (^) and (&)
- Mapped (-) and (=) to my dominant finger (right index)
- Mapped paranthesis' to the middle home row fingers

![Special keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-special-initial.png)

![Special-layer keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-special-layer.png)

This is surprisingly easy to adapt to and I actually prefer this parenthesis-layout over QWERTY's.

## Arrow keys and Function keys
Other small keyboard usually have the arrow keys in the bottom right corner.
This keyboard footprint doesn't allow for that, but I don't mind since we can do better.
Just like with numbers, they just magically appear under the right hand when we press "right shift". Clean and efficient.
Function keys are placed on the left side of this almost empty layer.

![Arrows keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-arrows-initial.png)

![Arrows-layer keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-arrows-layer.png)

## Making the keyboard complete
To finish up the layout i use some more QMK features which result in the following:

- The "escape key" is normally ESC, but now (~) when shift is pressed
- The Shift and Enter keys from before are combined into one: Enter when pressed, Shift when held down
- The Del key is now on the bottom right
- Layer 1 is updated
- Layer 4 is new

![QMK keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-qmk.png)

In addition to numbers this layer now has Media keys, a Power key, a Reset key and RGB control.

![QMK-numbers keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-numbers-qmk.png)

This layers allows for cursor control without a mouse.

![QMK-mouse keyboard](https://raw.githubusercontent.com/EdvardSire/keyboard/master/images/keyboard-layout-mouse.png)

## Todo
- Update images to be consistent with new keys added

keyboard

keyboard 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

keyboard

keyboard 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README