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

Simplify, update, detail keyboard customization #23

Merged
merged 53 commits into from
Aug 6, 2024

Conversation

bstiq
Copy link
Member

@bstiq bstiq commented Aug 1, 2024

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.

  • move how to compile your firmware from bk's bastardkb-qmk repo to the docs
  • after the build guides, link the users to a simple how to use page, which details daily use:
    • trackball info if relevant
    • link to default keymaps
    • link to advanced charybdis customization (if relevant)
    • how to customize the keyboard using VIA
    • link to advanced customization with QMK (with a "for advanced users" disclaimer)
  • new fw/compile-firmware.md page, updated with the removal of old hardware, which details how to compile your own firmware with QMK

I chose to give Using VIA more visibility by adding it directly at the end of each build guide, while the Using 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:

  • separate the charybdis and non-charybdis "customize" pages (no need for trackball use on the non-trackball keyboards)
  • remove empty MAX guide and add note in intro
  • add a dilemma v1 and v2 customize page that links to the charybdis' daily usage page
  • simplify the how to compile your firmware page to reflect removal of old hardware

_includes/use_keyboard_chary.md Outdated Show resolved Hide resolved
.wordlist.txt Show resolved Hide resolved
_includes/use_keyboard.md Outdated Show resolved Hide resolved
_includes/use_keyboard.md Outdated Show resolved Hide resolved
_includes/use_keyboard.md Outdated Show resolved Hide resolved
_includes/use_keyboard_chary.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
bstiq and others added 13 commits August 2, 2024 15:04
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>
.wordlist.txt Outdated Show resolved Hide resolved
.wordlist.txt Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
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.
Copy link
Collaborator

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.

Copy link
Member Author

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

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See suggestion below

fw/compile-firmware.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
fw/compile-firmware.md Outdated Show resolved Hide resolved
bstiq and others added 5 commits August 6, 2024 11:30
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 Show resolved Hide resolved
bstiq and others added 6 commits August 6, 2024 11:39
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>
@bstiq bstiq merged commit 9c573e6 into Bastardkb:master Aug 6, 2024
1 check passed
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