aboutsummaryrefslogtreecommitdiff
path: root/docs/hardware_keyboard_guidelines.md
diff options
context:
space:
mode:
authorskullY <skullydazed@gmail.com>2017-11-02 16:27:17 -0700
committerskullY <skullydazed@gmail.com>2017-11-02 16:27:17 -0700
commit535c2f60a9336d67c1a3fbd2d335b6f24d8cca8d (patch)
treeea0beb3f418ee9c20dcc21f83790d274928571e4 /docs/hardware_keyboard_guidelines.md
parent65eaab8a1a1c05fc03c54dd8827ce3ca8308301d (diff)
downloadqmk_firmware-535c2f60a9336d67c1a3fbd2d335b6f24d8cca8d.tar.gz
qmk_firmware-535c2f60a9336d67c1a3fbd2d335b6f24d8cca8d.zip
use real greater than and less than chars
Diffstat (limited to 'docs/hardware_keyboard_guidelines.md')
-rw-r--r--docs/hardware_keyboard_guidelines.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/hardware_keyboard_guidelines.md b/docs/hardware_keyboard_guidelines.md
index aedaa6301..8b16a13c9 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
20 20
21As 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. 21As 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.
22 22
23You can create `info.json` files at every level under `qmk_firmware/keyboards/&lt;name&gt;` 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%. 23You 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%.
24 24
25### `info.json` Format 25### `info.json` Format
26 26