-
Notifications
You must be signed in to change notification settings - Fork 3
contributing
Report errors, contribute sources and request hardware with enough evidence to review.
Use the pinout collection for incorrect labels, wrong models, missing sources or missing boards. Include the exact device and revision, guide record link, what appears wrong and manufacturer evidence. Identify the connector, pin or callout involved. Exclude private measurements and personal information.
- Prefer manufacturer documentation, original schematics, maintained board repositories or clearly identified original hardware evidence.
- State the model, revision, view orientation and connector scope.
- Include the source URL, author, license and collection date where known.
- Mark uncertainty and missing pins. Keep original image bytes and attribution.
- For a custom diagram, provide editable source and a per-pin evidence trail.
For broken search, display issues or desktop bugs, state the app version, platform, exact steps and expected result. Include the theme and window size for layout problems. A minimal reproducible report helps test the correction.
Describe the workbench task and where the guide slows you down. Failed search terms, hard-to-read diagrams and missing revision distinctions are especially useful. Hardware requests join the research queue; a request does not mean its pinout is already verified.
First Edition / 2026 · Open the guide · Source collection
- HaleHound and Elechouse hardware references
- Datasheets, I/O boards and carrier revisions
- ARM, x86 and RISC-V computers
- Start at the workbench
- How to read a pinout reference
- GPIO, I²C, SPI and UART
- Identify displays and sensors
- Use the Power Desk carefully
- Find a power-module reference
- Search, themes and saved boards
- Coverage, sources and review status
- Help improve the maker reference