Skip to content

add skji, skji/coquette (1209/FE80) #1078

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

ember-ana
Copy link

@ember-ana ember-ana commented Jul 29, 2025

Hiya!
This is a PID request for coquette, a keyboard @galaxyeden and I have been working on for the past 7 months (and have been daily-driving for about half of that time!)

It's a labor of love with many incremental improvements and learnings we along the way, that's finally at a point we consider release-ready.

The keyboard is split into board and shield, and we have multiple versions of each based on design preferences, hand measurements, etc.
All boards and shields under the coquette org were made from scratch in (mostly) KiCad.

All original creations are licensed under EUPL-1.2, and derivative works under their parent license (MIT, Apache2).

So this doesn't become a novel, the remaining facts & features as bullet points:

  • hours of anatomy (human, bird) & ergonomics research
  • different shield angles based on hand measurements
  • BLE using nRF5340 (instead of the way more common rRF52840 – gets us some better bluetooth perf)
  • ridiculous power optimization (2+ months of daily use, depending on battery size)
  • LED underglow on board & shield (literally glows because we're using UV LEDs against neon acrylic)
  • expandable using STEMMA QT and Shitty Add-On V1.69bis
  • very pretty PCBs

@galaxyeden
Copy link

I've been the hardware design person on this and this is currently at the state of an open source hardware project anyone can build though there is some firmware work required for some of the features (I'm working on this and plan to have at least mostly feature-complete firmware soon), and because it's now at a state anyone can build it, and we have working hardware, I wanted us to get a real PID code to use, to explain further why! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants