Hidden-layer intro preview with the toggle highlighted (extras.adomLayer.intro) + a hero-GLB authoring skill (layers, tooltips, animation and viewer_3d knobs in one page)
Two asks from John (2026-09-19), found while building the VL53L5CX / VL53L7CX / VL53L8CX hero GLBs
1. Intro preview of a hidden layer, with its toggle highlighted
These ToF sensors ship their field-of-view cones inside the manufacturer STEP. In the hero GLB (adom/vl53l5cx, vl53l7cx, vl53l8cx: <slug>-hero.glb) the cones are a node named Adom.FOV declared as a layer:
"extras": {"adomLayer": {"key": "fov", "label": "Field of view", "group": "Optics", "hidden": true,
"intro": {"fadeInAt": 1.5, "fadeOutAt": 6.5, "highlightButton": true}}}
hidden: true already gives the toggle (adom/wiki#95, #162). The intro object is a proposal: when the model loads, briefly fade that hidden layer in (about 1.5 s to 3 s), hold, fade it out by about 6.5 s, and while it is visible render its Layers-panel toggle as pressed / pulsing, so the reader learns "I can switch the field of view on". After the intro the layer rests hidden and the button rests off. John's words: "fade in for a second and then fade out, but hilite the button as if it's on when you fade in the fov so the user knows, oh, I can toggle the field of view on in this hero GLB."
The GLBs also carry a looping glTF animation adom-hero-intro (a gentle plus/minus 6 degree yaw of the root, 24 s period) that plays today through the autoplay path. A material fade cannot be expressed in core glTF; I can add KHR_animation_pointer channels on the FoV materials' baseColorFactor if the viewer's Babylon build honours that extension, but the button highlight can only come from the viewer, so the intro declaration on the layer is the cleaner contract.
Also still wanted from adom/wiki#57's follow-up: a small play / pause control so a reader can replay an intro after it settles.
2. A "hero GLB" skill so every author gets this right
There is no installed skill that documents what the wiki 3D viewer reads from a GLB. I had to reconstruct it from adom/wiki#95, #162, #57, #55, #48 and docs/CONTENT-CONVENTIONS.md. Please ship (in adom-wiki-skillpack next to wiki-component, or as the viewer's own skill) one page that covers:
extras.adomLayer {key, label, group, hidden}: nearest declaring ancestor per mesh, the two-layer minimum for a panel, the built-in vocabulary (fr4_board,pad_top,solder_top,silk,barrel,pin1_marker) and how declared layers compose with it, the (proposed)intro.extras.tooltip,onMeshHoversuppression of internal CAD names, pin cross-highlight naming (pad_N/lead_N).- Animation: which groups autoplay,
component.viewer_3d {repeat, loop, animate, ground}in page.json and the?repeat= ?loop= ?animate= ?ground=query knobs, whetherKHR_animation_pointer/KHR_materials_*are honoured, how the hero vs plain model ("3D | Hero" buttons) are chosen fromcomponent.parts. - Materials: alphaMode BLEND and doubleSided for translucent artwork, quantization, Draco.
- Node naming that survives service-step2glb (instance labels,
Adom.*groups) and the hero-only vs board-LOD split.
Working examples to point at: the three VL53Lx hero GLBs (six declared layers each: Chip, MPN etch, Field of view (hidden), Pad outlines, Silkscreen, Pad labels; yaw animation) and the tooling that made them, pipeline/ on adom/vl53l5cx (hero_step.py, glb_alpha.py).