Kezewa Enter67 Mechanical Keyboard Kit - Drop Exclusive

My implementation for sure is not ideal. I also never worked with QMK in cases other than changing keymap. But I'm looking more and more into QMK and ZMK (First time hearing about KMK!) If someone is skilled in QMK then I would be glad for PRs with improvements! At the end the goal is to get this keyboard working as advertised for everyones benefit. :)

Good call! Thanks for updating and tagging me. I'm still learning the quirks of QMK/KMK/VIA/VIAL :) I finally figured out to use RGBMATRIX while debugging a different keyboard (MF17) and haven't gone back to update this kb yet (to self: this is my reminder to do so) ---------------------------------------------------------------------------------------------------- However, for anyone wanting to use RGBLIGHT for doing a pseudo-'per-key' lighting based on layers, using the config.h in my other post, you can do something like this in your keymap.c: const rgblight_segment_t PROGMEM my_fist_layer[] = RGBLIGHT_LAYER_SEGMENTS(    {1, 10, HSV_GREEN},    {13, 1, HSV_ORANGE},    {45, 1, HSV_RED},    {46, 2, HSV_BLUE},    {48, 2, HSV_PURPLE},    {50, 2, HSV_MAGENTA} ); const rgblight_segment_t PROGMEM my_second_layer[] = RGBLIGHT_LAYER_SEGMENTS(    {1, 10, HSV_GOLD},    {25, 1, HSV_SPRINGGREEN},    {39, 1, HSV_TURQUOISE},    {53, 1, HSV_ORANGE} ); //Later layers take precedence const rgblight_segment_t* const PROGMEM my_rgb_layers[] = RGBLIGHT_LAYERS_LIST(    my_first_layer,    my_second_layer  ); void keyboard_post_init_user(void) {    // Enable the LED layers    rgblight_layers = my_rgb_layers; } layer_state_t layer_state_set_user(layer_state_t state) {    rgblight_set_layer_state(0, layer_state_cmp(state, 1));    rgblight_set_layer_state(1, layer_state_cmp(state, 2));    return state; }

You can try my firmware https://drop.com/buy/kezewa-enter67-mechanical-keyboard-kit/talk/2950555