Skip to content
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

Better Documentation around configs #2534

Open
SamBobBarnes opened this issue Oct 4, 2024 · 1 comment
Open

Better Documentation around configs #2534

SamBobBarnes opened this issue Oct 4, 2024 · 1 comment

Comments

@SamBobBarnes
Copy link

I ran into an issue recently that could have been mitigated with some teaks to the documentation.
Specifically, https://zmk.dev/docs/config. It would have helped a ton to have an example file structure for a minimal config. I was tripped up because I didnt understand that the my-keyboard.conf file needed to belong in the config folder rather than the shield/my-keyboard folder.

@caksoylar
Copy link
Contributor

caksoylar commented Oct 4, 2024

Where did you initially come across adding that file? I am asking because although we have it documented in a few places, it is still a frequent footgun for users.

For reference, the config page mentions:

Shared config files (excluding any _left or _right suffix) are not currently supported in shield folders.

New shield docs have this note (if you select the split tab):

The shared configuration in my_keyboard.conf is only applied when you are building with a zmk-config folder and it is present at config/my_keyboard.conf.

I'd say that maybe moving that remark next to "Configuration elements affect both halves" would be better.

It would have helped a ton to have an example file structure for a minimal config.

This is a good idea, I can see that helping in https://zmk.dev/docs/development/hardware-integration/new-shield#new-shield-directory.

For the Configuration Overview page, maybe adding tabs for non-split/split (and/or ZMK/config/module) would make it clearer in which cases it applies to.

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

No branches or pull requests

2 participants