qmk/qmk_firmware
1
0
Fork 0
mirror of https://github.com/qmk/qmk_firmware.git synced 2026-10-01 22:40:11 +02:00
Code Issues Packages Projects Releases Wiki Activity

add docusaurus, convert notes/tips, ids

Browse Source
This commit is contained in:
Jack Humbert
2023-04-18 12:35:09 -04:00
parent e0a09ff728
commit 2cef3465e8
180 changed files with 15192 additions and 785 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/hardware_keyboard_guidelines.md
+15 -3
View File
@@ -130,7 +130,11 @@ The `post_config.h` file can be used for additional post-processing, depending o
#endif
```
?> If you define options using `post_config.h` as in the above example, you should not define the same options in the keyboard- or user-level `config.h`.
:::tip
If you define options using `post_config.h` as in the above example, you should not define the same options in the keyboard- or user-level `config.h`.
:::
### `rules.mk`
@@ -177,7 +181,11 @@ The `post_rules.mk` file can interpret `features` of a keyboard-level before `co
endif
```
?> See `build_keyboard.mk` and `common_features.mk` for more details.
:::tip
See `build_keyboard.mk` and `common_features.mk` for more details.
:::
### `<keyboard_name.c>`
@@ -208,7 +216,11 @@ As an example, if you have a 60% PCB that supports ANSI and ISO you might define
| LAYOUT_ansi | default_ansi | An ANSI layout |
| LAYOUT_iso | default_iso | An ISO layout |
?> Providing only `LAYOUT_all` is invalid - especially when implementing the additional layouts within 3rd party tooling.
:::tip
Providing only `LAYOUT_all` is invalid - especially when implementing the additional layouts within 3rd party tooling.
:::
## Image/Hardware Files