diff options
| author | skullY <skullydazed@gmail.com> | 2017-11-02 16:27:17 -0700 |
|---|---|---|
| committer | skullY <skullydazed@gmail.com> | 2017-11-02 16:27:17 -0700 |
| commit | 535c2f60a9336d67c1a3fbd2d335b6f24d8cca8d (patch) | |
| tree | ea0beb3f418ee9c20dcc21f83790d274928571e4 | |
| parent | 65eaab8a1a1c05fc03c54dd8827ce3ca8308301d (diff) | |
use real greater than and less than chars
| -rw-r--r-- | docs/hardware_keyboard_guidelines.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/hardware_keyboard_guidelines.md b/docs/hardware_keyboard_guidelines.md index aedaa6301c..8b16a13c9b 100644 --- a/docs/hardware_keyboard_guidelines.md +++ b/docs/hardware_keyboard_guidelines.md @@ -20,7 +20,7 @@ Any sort of hardware file (plate, case, pcb) can't be stored in qmk_firmware, bu As QMK grows so does the ecosystem surrounding QMK. To make it easier for projects in that ecosystem to tie into QMK as we make changes we are developing a metadata system to expose information about keyboards in QMK. -You can create `info.json` files at every level under `qmk_firmware/keyboards/<name>` to specify this metadata. These files are combined, with more specific files overriding keys in less specific files. This means you do not need to duplicate your metadata information. For example, `qmk_firmware/keyboards/clueboard/info.json` specifies `manufacturer` and `maintainer`, while `qmk_firmware/keyboards/clueboard/66/info.json` specifies more specific information about Clueboard 66%. +You can create `info.json` files at every level under `qmk_firmware/keyboards/<name>` to specify this metadata. These files are combined, with more specific files overriding keys in less specific files. This means you do not need to duplicate your metadata information. For example, `qmk_firmware/keyboards/clueboard/info.json` specifies `manufacturer` and `maintainer`, while `qmk_firmware/keyboards/clueboard/66/info.json` specifies more specific information about Clueboard 66%. ### `info.json` Format |