by adom
The one-stop-shop for publishing a hardware component (or molecule/board) to the Adom Wiki. The whole lifecycle: page anatomy, the clone→edit→preview→push loop and its hard rules, making a great hero image (Hero Component Studio — 16:10, overlay-safe, datasheet-backed), the animated 3D composite, the interactive 3D viewer, ct thumbnails, the datasheet-accuracy audit, and every wiki push/pull gotcha we've hit. Now includes the worked Path B (board) pipeline: STEP-to-GLB, refdes tagging, layer de-
← Commit history
Merge PR #170: Visibility default: match the board (public unless the board is private), not a hard --private
1 file changed
+13−4
SKILL.md+13−4@@ -28,7 +28,11 @@ right.** "Component" here means any physical thing that gets a wiki page: a disc > section, bump the version, and open a PR against `adom/adom-hardware-component-publish`. Never > re-solve a problem that's already written here. -> **Private / Adom-only.** Published under the `adom` org, visibility private.+> **Published under the `adom` org. Visibility MATCHES THE BOARD: public unless the board the+> part hangs off is private.** A standalone component page (no board) is public. The old text+> here said "visibility private" for everything, and that is how 66 connectors, resistors and+> caps ended up private on the org with public pages depending on some of them (2026-09-18).+> `--private` is for parts of a private board, never a default. > **First decide which kind of page you're making** — a single **COMPONENT** (Path A) or a full > **BOARD / MOLECULE** (Path B). The required contents differ (see "Two kinds of page" below). On a@@ -318,7 +322,8 @@ adom-wiki page hero <owner>/<slug> --image screenshots/hero.png # NOTE: no -- # --- NEW page: scaffold + publish --- adom-wiki pkg init <slug> --type component-adom-wiki pkg publish --org adom --private -m "<changelog>" # from the pkg dir+adom-wiki pkg publish --org adom --public -m "<changelog>" # from the pkg dir; default+adom-wiki pkg publish --org adom --private -m "<changelog>" # ONLY for a part of a PRIVATE board (rule 6) ``` **Verify a pushed asset authenticated** (private pages 403 unauthenticated — see 8h):@@ -764,8 +769,12 @@ fine but shows up in the Project Manager with no BOM panel. The graph is depender publishes. Merge everything *before* the board's publish so the cycle produces exactly one registry version. MERGE deps, never overwrite (`component`, `hero`, `tags`, `model_3d_path` must survive).-6. **Inherit the board's visibility.** A private board's library and component pages are published- **`--private` to the same org** — a public part page hanging off a private board leaks the design.+6. **Match the board's visibility, both ways.** A private board's library and component pages are+ published **`--private` to the same org** — a public part page hanging off a private board leaks+ the design. A public board's parts are **public**, and a part used by any public board or molecule+ is public even if it also sits on a private one (the public page already names it). When a board+ is flipped public later, flip its library and parts with it: a public board linking to private+ parts is the failure this rule exists to prevent, seen from the other side. **Completion checklist (a Path B publish is NOT done until all pass):**