-
-
Notifications
You must be signed in to change notification settings - Fork 39.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for Xlant XL keyboard #24608
base: master
Are you sure you want to change the base?
Conversation
for the release 1 of this keyboard.
Co-authored-by: jack <[email protected]>
Co-authored-by: jack <[email protected]>
Co-authored-by: jack <[email protected]>
Co-authored-by: jack <[email protected]>
applied `qmk format-json -i` on keyboard.json to conform with the project formatt standards.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this keyboard is made/sold by 1upkeyboards, it should probably live with the rest of the keyboards under keyboards/1upkeyboards/...
.
Co-authored-by: jack <[email protected]>
Co-authored-by: jack <[email protected]>
Co-authored-by: jack <[email protected]>
Regarding the 1UpKeyboards folder, I noted that they sell the Zlant keyboard (https://1upkeyboards.com/shop/keyboard-kits/diy-40-kits/zlant-40-keyboard-pcb/), which lives in QMK in the main keyboards folder. That's why I kept the Zlant XL at the same level. |
Ah, I suppose it looks like the ZlantXL was designed/sold outside of 1upkeyboards originally (Reddit post). So I suppose its current location is more appropriate. |
The change includes the keyboard layout, data driven with .json file, and a default layout as a starting point to customize a board.
Description
The change include a new main folder
zlant_xl
for a single keyboard.The keyboard is fully configured via a keyboard.json file. In addition a default layout is provided.
Types of Changes
Issues Fixed or Closed by This PR
Checklist