-
Notifications
You must be signed in to change notification settings - Fork 7
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
Simplify, update, detail keyboard customization #23
Conversation
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
fw/compile-firmware.md
Outdated
This page details how to compile your own firmware. Building from source is useful to people who want to customize their keyboard and keymaps beyond what Via offers. This involves using a command-line interface, writing C code, and compiling this code into the final firmware file. | ||
This page details how to build your own firmware. | ||
Building from source is useful to people who want to customize their keyboard and keymaps beyond what Via offers. | ||
You will have to modify the keymap `C` code, and from there compile your firmware either using Github actions or the local command line. | ||
|
||
If that seems too complicated, you can also use one of the default releases, or VIA. |
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.
Doesn't one include the other? Perhaps "you can also use one of the defalult releases using via".
"default releases" should also link to the releases page.
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.
added release link. not sure what you mean with the other
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.
See suggestion below
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
Co-authored-by: burkfers <finrod09@users.noreply.github.com>
This PR has an overall goal of detailing more and simplifying more the process of using and customizing your keyboard.
Until now, everything was a bit mish-mashed, so better separation was needed. The documentation on how to compile your firmware was also outdated.
how to compile your firmware
from bk's bastardkb-qmk repo to the docshow to use
page, which details daily use:fw/compile-firmware.md
page, updated with the removal of old hardware, which details how to compile your own firmware with QMKI chose to give
Using VIA
more visibility by adding it directly at the end of each build guide, while theUsing QMK
get its own page. This makes the pages less information-heavy, and we can be more detailed on the QMK pages.On top of this, overall cleanups:
how to compile your firmware
page to reflect removal of old hardware