Feature: Collect keyboard-layout-editor templates

[precondition]

There is currently no centralized repository of KLE (https://keyboard-layout-editor.com/) templates/presets (aside from the few presets available on the site). To simplify the process of getting a starter KLE preset for one's keyboard, it would be nice to create a tab/sub-page on KeymapDB.com that gathers many KLE presets and tags them with the associated keyboard properties (e.g. keyboard name, stagger type, key count, split or not, ...).

All templates would be standardized by displaying only one layer of unstyled Black-on-White keycaps where all keycaps are left blank except for the 26 letters of the alphabets laid out in the most likely QWERTY formation.

This feature could potentially be generalized to support other visualization “engines” like keymap-drawer. The QMK Configurator could also be seen as a visualization engine but it does not support showing multiple legends on the same key and most importantly, it already includes a comprehensive dropdown including all supported QMK keyboards shipped with the default keymap so there is no discoverability issue and copying the QMK Config keymaps on KeymapDB.com would bring no added value.

[caksoylar]

I think that'd be nice. KLE is most likely still the choice for such a thing but ensuring coverage for all the weird ergo keyboards will be a lot of work.

To add on a bit, keymap-drawer mainly uses QMK style layout definitions as well, where it piggy-backs on QMK's API to fetch the layouts if layout is specified by QMK keyboard name. I also maintain an extra list of layouts in the same format to override QMK ones (e.g. for keyboards with rotated thumb keys) and add ones that aren't in QMK. I'd really want it to be a community-contributed resource but I haven't had too many user contributions.

[precondition]

I think that'd be nice. KLE is most likely still the choice for such a thing but ensuring coverage for all the weird ergo keyboards will be a lot of work.

To add on a bit, keymap-drawer mainly uses QMK style layout definitions as well, where it piggy-backs on QMK's API to fetch the layouts if layout is specified by QMK keyboard name. I also maintain an extra list of layouts in the same format to override QMK ones (e.g. for keyboards with rotated thumb keys) and add ones that aren't in QMK. I'd really want it to be a community-contributed resource but I haven't had too many user contributions.

@caksoylar If keymap-drawer builds on the keyboard info.json in a similar way to the QMK configurator, is there a value to cataloguing keymap-drawer templates on KeymapDB? If all the layout definitions are natively available via a simple --qmk-keyboard option, there is no discoverability issue.

[caksoylar]

No, there shouldn't be a need to maintain a separate list of files as templates. However if there ends up being a database of KLE templates, adding a pointer like "Equivalent keymap-drawer physical layout: qmk_keyboard: ferris/sweep" to each might be nice (I can definitely help with this).