It’s easy with all keys controlled by index and middle fingers, but pinky and ring are tougher since it involves vertical movement that I’m not used to. Muscle memory tries to get my left ring finger to jump around and do all the work, but its faster to use my pinky for A and Z. I still jump with Q.

I feel that columnar is already so much more efficient and comfortable than staggered. I also could never give up layer functionality with this layout now that I’m getting the hang of it. Everything I need is already within reach and in a natural layout.

I’m surprised it’s easy for you to go back to staggered, I already find it so weird to pick up my old mech keyboard! My laptop though seems much easier but I guess that’s because it has flat keys?

Heck yes on the middle layer! Per key RGB was a bit tricky and I think I understand it, but the entirety of my code is in my repo. Definitely reference that. With the assumption that you have QMK set up:

1. Enable RGB matrix lighting and optional tap dance for some shortcut fun in rules.mk
2. #define SPLIT_LAYER_STATE_ENABLE, #define EE_HANDS, and #define RGB_MATRIX_KEYPRESSES in config.h
3. State your safety net for max/min led range so it doesn't loop infinitely and use rgb_matrix_indicators_advanced_user to set up some if statements.

An example - on my layout, I have E, S, D, F as my arrow keys on my second layer.

if (i == 8 || (i >= 14 && i <= 16)) {

RGB_MATRIX_INDICATOR_SET_COLOR(i, 250, 55, 55);

}

With this if statement, i represents the key codes I'm targeting (see image below). || separates each range as "or". So if my range is (8) or (≥ 14 and ≤ 16), i then is defined with that RGB color code. Basically pink. Or you can say (i, RGB_PINK) or any other defined RGB string you can find in the QMK documentation.

Everything after the RGB LED Setup divider in my code is just there for per key rgb on any layer above 0, plus my simple tap dance command to double tap the shift key and turn it red when caps lock is enabled. DM me if you have any questions!

Edit, also! Here's the LED map for each key for when you define your ranges. Hope this helps.

https://preview.redd.it/yvldam3nthja1.png?width=640&format=png&auto=webp&v=enabled&s=4fbb9a7ebfe0110cfd55a34678d4fec909a2305c

Thank you! I got the white acrylic plates and frosted acrylic middle layer. They still have them! I was thinking of waiting for another release of the white aluminum case, but it really does look awesome having the light shine through the middle with the frosted layer.

Perhaps down the line I will, but I grew up with qwerty and am very quick with it! If it's just a matter of learning where to reposition fingers to type, that's a lot easier than completely relearning.

Of course! Please do DM me if you need help. It took me ages to get this to work properly and there isn't much out there on Irises aside from the more advanced QMK documentation on RGB matrix lighting.

It's hard to say no! The iris kits are at a decent price if you're looking at split ergos. Not including the switches and caps though, I guess it all adds up the same ha.

>P.S. it's great when you have cats who love to sit right in front of you: you can just move the halves and still type just fine while receiving kisses.

Clearly the only reason I got a split. Kitty comfort top priority.

Ha well at least it'd look cool on your desk!

Yes! I just updated my git repo with my latest rev. Keep in mind it's very simplified. I really don't know this language well but hey, this does what I need it to so I'm not going to mess with it anymore.

Credit to kahgoh on git for the bones of the RGB code and his awesome tutorial on finding the LED indexes for the Iris. This writeup was SO helpful. He made a map you can find at the end of the article that illustrates the default layout's snaking order. He also mentions the indexes for the underglow LEDs in that guide.

This was a semi DIY - Keebio sells the finished PCB board (soldered, hot swap, flashed) but I also had to purchase the top and bottom plates and optional middle layer. It took about an hour to put together, their documentation is very helpful! I also got some tall cone bumpers to angle both sides slightly since I didn't love the tenting system they suggested from ErgoEZ. Keycaps and switches are separate. Also forgot to mention I added some blank white keycaps since I needed those little tactile bumps on the surface to help with my thumb orientation.

Great idea!

So far a few lessons on Keybr have done wonders. I still stumble with V, X, and Z and of course all the new modifiers and symbols. My typing speed was originally 110 wpm on a good day and I'm at around 90 already. It's surprisingly intuitive and wildly more comfortable on the wrists and hands! I feel like Alices are similar to this, I'd say go for it.

Layer 2 reminds me of the location of all my brackets and symbols for web dev, arrow keys, and num pad. Not color coded are media controls and F keys. I also set up color-indicated caps lock with tap dance on my shift key. Took a couple days to learn C basics and stumble through QMK docs, but I'm thrilled with the result!! I couldn't have done it without the community. (Edited keeb deets x2)

Git repo for keymap and config edits - I am no pro, use at your own risk

Keycaps: Amazon LTC Lava Caps PBT Pudding - they don't sound great, too clacky, but I can't find any other shine-throughs that I want to stare at all day

Blank keycaps for thumb keys: Amazon YMDK Keys - these actually sound and feel amazing?!

Switches: Gateron Black Inks 2.0 lubed, filmed, modded with 45g springs - I get the occasional accidental key presses, but I'm a light touch typer. These are way better than the stock 70g for me!

Rubber cone feet for minimal tent: Amazon rubber bumpers

https://preview.redd.it/cfmu9misebja1.jpeg?width=3736&format=pjpg&auto=webp&v=enabled&s=f209cabdac68dbc59177328c76e8e98dfa68a9a8