[Keyboard] Refactor JJ50 keyboard mapping to current standard

[GreatWizard]

Description

• [Doc] Update main README (https://github.com/GreatWizard/qmk_firmware/blob/update_default_jj50/keyboards/jj50/README.md)
• [Doc] Add README about the default keymaps (https://github.com/GreatWizard/qmk_firmware/blob/update_default_jj50/keyboards/jj50/keymaps/default/README.md)

• [Feature] Add Dvroak, Colemak as base layers

• [Feature] Add an Adjust layer to change the base layer
• [Enhancement] Update the mappings in all the layers to follow the default 5x12 ortholinear preonic
• [Enhancement] Update Fn mapping to have all rgblight and backlight features

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[fauxpark]

With the changes to the archetype keymap this PR must go through the breaking changes process. If you don't mind this, you can actually outright delete that rules.mk as it's identical to the keyboard-level one.

[GreatWizard]

I can't delete the rules.mk for the archetype keymap, there is 2 more rules then the keyboard-level one:

TAP_DANCE_ENABLE = yes
AUTO_SHIFT_ENABLE = yes

[fauxpark]

Ah, well you can delete everything else then.

[GreatWizard]

The CI is having a hard time with xvzver, returning error: NKRO not supported with this protocol
And I have no idea why, NKRO is disabled in JJ50 rules

[fauxpark]

layouts\community\ortho_5x12\xyverz\rules.mk is meant to check whether PROTOCOL is VUSB, which is set in quantum/mcu_selection.mk however the rules.mk is actually evaluated first. You can safely ignore that for now.

[GreatWizard]

My latest commit adapt a bit the workflow... I'm not sure if there is any blockers by changing the order?

Can we talk somewhere else in order to chat about the subject? (discord irc slack...)

[fauxpark]

Interesting that that seems to work, considering mcu_selection.mk first needs to know what MCU is, which is defined in rules.mk. I suppose it must have to do with when make evaluates stuff. In any case, that should really be done in a separate PR.

The QMK Discord is linked in the readme (it's one of the badges) but I'll post it here too: https://discord.gg/Uq7gcHh

[GreatWizard]

the CI is going well indeed 😊
I will definitively opening a PR only for that change

[fauxpark]

Well you've now added a core change to this PR so Travis is going to run make all:default instead of make <changedkeyboards>:all.

[GreatWizard]

I made the PR #9419
I will rebase this one when the other is merged
let's continue to talk about the "fix" over there and keep this PR related to JJ50 keymaps ^^

[noroadsleft]

Just some minor fixes.

[GreatWizard]

Tested and it works like a charm :)
🎉

[aaarsene]

I justed tested it and everything seems to work like it should!