by adom
How the Adom Wiki (wiki.adom.inc) works and how to drive it with the adom-wiki CLI: the two storage layers (git page repo vs package registry), hosting source by pushing files (not a tarball), making packages, cutting per-platform releases, and the three-tier skill layout (user skills ship, dev-skills/ and publish-skills/ stay source-only). adom-wiki is the current tool; adompkg is deprecated.
Component pages: use a shared symbol from another page, so a symbol fix reaches every part that uses it
Feature request, 2026-11-04, signed in as ray.
Ask. Let a component page use a shared symbol from another page instead of carrying its own copy, so that changing the shared symbol changes every part that uses it.
Why. Every component page carries its own .kicad_sym and .lbr. Thousands of parts share one symbol in practice: every resistor is the same zigzag, every capacitor the same two plates. Today a symbol fix means a push to every page. Right now that is about 27,800 pushes:
| Symbol fault | Pages |
|---|---|
| Two-pin parts drawn as a box with pins "1" and "2" instead of the standard symbol (diodes 13,898, inductors 4,829, resistors 1,514, fuses 1,260, capacitors 739, other 3,569) | 25,809 |
| Pin names drawn over each other (e.g. adom/ny8a054es8, pin 4's name over pin 5's) | 2,029 |
Colby found both from seven random parts. The factory is fixed for new parts (component-page-verify 0.4.0 fails the second fault). The existing pages still need the push. With a shared symbol, the resistor fix would be one edit instead of 1,514.
A possible shape. This follows the built_from provenance from #203, but for content rather than history:
"component": {
"parts": {
"symbol": { "from": "adom/symbol-resistor-us", "name": "R_US" }
}
}
- The wiki serves the shared page's current symbol in the page's symbol viewer, in
files/<slug>.kicad_symand in the.lbrdownload. It renames the symbol and sets Value, MPN, Datasheet and distributor properties from the part's ownpage.json, so a download still reads as this part. - The pin to pad map stays on the part's page (
component.pins), so a shared symbol never decides which pad is which. - The part page shows which shared symbol it uses and its revision, and the shared page lists the parts that use it, like #203 does for molecule families.
Open questions.
- Should a download keep a per-part file (fixed when downloaded), or always fetch the shared one?
- Should a part be able to pin a revision of the shared symbol, so a bad edit doesn't reach thousands of pages at once?