The Corne keyboard is a split keyboard with 3x6 column staggered keys and 3 thumb keys, based on Helix. Crkbd stands for Corne Keyboard. Foostan

[Deskmat is called Mizu Deskmat: Water]

This keyboard was bought from Little Keyboards with an assembly service included since I did not have the tools nor the confidence to solder the board flawlessly 💸💸.

A summary of features that have been changed:

This personalized keymap is based on my Ergodox EZ layout which uses the thumb keys for multiple actions. For example, typing on the spacebar will return a space character but holding it will make it act as a CTRL key.

These are the Features that are needed for the keyboard:

This keymap has been developed for a Corne keyboard containing:

Here are the full details of the keyboard (if you are interested):

The master OLED displays:

• the active layer;
• the matrix coordinates and keycode;
• LED Indicators (only Num Lock and Caps Lock);
• WPM counter;
• WPM graph.

The slave OLED displays:

• the Corne logo;
• HSV values;
• and my favorite mascot.

The glcdfont has been modified to display Kapibara-san, a Japanese cartoon character representing a capybara with a moving animation based on WPM.

To edit the glcdfont, I recommend using the QMK Logo Editor by joric which helps a lot.

This is for a regular (standard) / home / everyday keymap layout:

# Left side
make crkbd:lazyproof:dfu-split-left

# Right side
make crkbd:lazyproof:dfu-split-right

For coding on an OSX environment with shortcuts meant for web debugging:

make crkbd:lazyproof:dfu-split-<left|right> TEMPLATE=code

For a one-sided keyboard that acts as an emoji dashboard (more will be explained in the Templating section):

make crkbd:lazyproof:dfu-split-right TEMPLATE=discord SIDE=right

This is a proof of concept that uses the 2 microcontrollers to their full extent.

• Each microcontroller will have the same configuration for:
  • layers;
  • OLED display;
  • and RGB config.
• Only the keymapping would change based on the arguments written on the console.

Plugging the left side keyboard and running:

make crkbd:lazyproof:dfu-split-left TEMPLATE=code

Then plugging the right side:

make crkbd:lazyproof:dfu-split-left TEMPLATE=discord SIDE=right

From there, plugging the keyboard on the left side would mean using the default template for the entire keyboard.

To go straight to the discord macros, plug on the right side of the keyboard.

• More customization possibilities for one-handed keyboards or simple keymaps.
• The lazy hardware version of TO(layer) (direct switch to a layer).
• More keymaps can be added if the OLED and RGB configuration for each layer remains the same.
• Easier to experiment with new keymapping by using one side of the keyboard: one side for the original, the other side for a lab experiment. No need to stash changes, recompile the correct version, or switch branching.

• Cannot have a different OLED or RGB config otherwise the keyboard will have layer behavior discrepancy: each has their brain and won't display their lights / OLED normally.
• Could add more layers but doesn't scale well: adding a new layer would possibly mean editing all the templates (UNLESS there's an RGB and OLED configuration for each template).
• Not futureproof: it's a hassle to maintain and to remember which template is used on which keyboard side.