Adom Wiki
Public Made by Adomby 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. Read this first before publishing or installing.
Widget registry: optional allow field (fullscreen, picture-in-picture) for widget frames
Ask. Let a registered widget request iframe permissions, so a video widget can go fullscreen like YouTube.
Why. ::adom-video (new in adom/widgets, a YouTube-style player) has F / double-click / a fullscreen button. Widget frames are created without allow/allowfullscreen (in app.js only slots with data-slot-allow get them; data-slot-sandbox="allow-scripts" for widgets), so document.fullscreenEnabled is false inside the frame. The widget currently falls back to opening its own frame URL full-window in a new tab, where F is real fullscreen. That works, but readers expect fullscreen in place.
Proposal. An optional allow field on a widgets.json entry, allowlisted to safe features (fullscreen, picture-in-picture, maybe clipboard-write), copied to the slot as data-slot-allow so the existing app.js path sets allow + allowfullscreen. The registry review stays the trust gate. adom-video would then register "allow": "fullscreen; picture-in-picture".
Precedent: #86 (3D viewer fullscreen) used the same slot mechanism.