add docusaurus, convert notes/tips, ids

docs/reference_configurator_support.md

@@ -21,7 +21,11 @@ To understand how the Configurator understands keyboards, first one must underst
 |---------------|
 ```
 
-?> For more on layout macros, see [Understanding QMK: Matrix Scanning](understanding_qmk.md?id=matrix-scanning) and [Understanding QMK: Matrix to Physical Layout Map](understanding_qmk.md?id=matrix-to-physical-layout-map).
+:::tip
+
+For more on layout macros, see [Understanding QMK: Matrix Scanning](understanding_qmk.md?id=matrix-scanning) and [Understanding QMK: Matrix to Physical Layout Map](understanding_qmk.md?id=matrix-to-physical-layout-map).
+
+:::
 
 The Configurator's API reads the keyboard's `.h` file from `qmk_firmware/keyboards/<keyboard>/<keyboard>.h`. For our numpad, this file would be `qmk_firmware/keyboards/numpad/numpad.h`:
 
@@ -65,9 +69,17 @@ QMK uses `KC_NO` to designate places in the switch matrix where there is no swit
 }
 ```
 
-!> This usage differs from that of keymap macros, which almost always use `XXXXXXX` (seven capital X's) for `KC_NO` and `_______` (seven underscores) for `KC_TRNS`.
+:::caution
 
-!> To prevent user confusion, using `KC_NO` is preferred.
+This usage differs from that of keymap macros, which almost always use `XXXXXXX` (seven capital X's) for `KC_NO` and `_______` (seven underscores) for `KC_TRNS`.
+
+:::
+
+:::caution
+
+To prevent user confusion, using `KC_NO` is preferred.
+
+:::
 
 The layout macro tells the Configurator that our keyboard has 17 keys, arranged in five rows of four columns each. Our switch positions are named `k<row><column>`, counting from 0. The names themselves actually don't matter, as long as they match between the top section, which receives the keycodes from the keymap, and the bottom half which designates where each key is in the matrix.
 
@@ -141,7 +153,11 @@ The `layouts` object contains the data that represents the physical layout of th
 
 Some objects will also have `"w"` and `"h"` keys, which represent a key's width and height, respectively.
 
-?> For more on the `info.json` files, see [`info.json` Format](reference_info_json.md).
+:::tip
+
+For more on the `info.json` files, see [`info.json` Format](reference_info_json.md).
+
+:::
 
 
 ## How the Configurator Programs Keys