pwarren/zmk_mf68
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: faq: Add preface links to "Why boards and shields?" [#22 CR, #11]

Browse source
This commit is contained in:
innovaker 2020-06-13 19:49:28 +01:00
parent c14beb7ee7
commit 726b40cfa2
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/docs/faq.md
View file

@ -60,6 +60,10 @@ In ZMK, a *shield* is a *PCB* or *hardwired set of components* that when combine
### Why *boards* and *shields*? Why not just “keyboard”? ### Why *boards* and *shields*? Why not just “keyboard”?
If you haven't already done so, please read these FAQs first:
- [What is a “board”?](#what-is-a-board)
- [What is a "shield"?](#what-is-a-shield)
When a keyboard accepts a small “PCB MCU module” (e.g. *Arduino Pro Micro*) for its “brains”, then it's important to conceptually separate the hardware into a *board* PCB and a *shield* PCB. When a keyboard accepts a small “PCB MCU module” (e.g. *Arduino Pro Micro*) for its “brains”, then it's important to conceptually separate the hardware into a *board* PCB and a *shield* PCB.
The *shield* is a brainless shell containing all the keys, RGB LEDs, encoders etc. It maps all of these features to a standard pin footprint, such as the Pro Micro pinout. The *shield* is a brainless shell containing all the keys, RGB LEDs, encoders etc. It maps all of these features to a standard pin footprint, such as the Pro Micro pinout.