Widget Registry

The reviewed list of widgets any wiki page can render from plain markdown (adom/wiki#152). Only widgets in widgets.json on THIS page render; adding one is an edit someone reads. That list is the entire trust model, so this page stays org-owned.

Using a widget

On its own line in any README.md:

::adom-pinout{src="/ray/stm32f103c8t6/render/pinout.json" layout="dual"}

An entry marked "render": "inline" (every current widget) renders in place as its custom element, with the reader's session. Any other entry renders as a sandboxed frame: opaque origin, storage shimmed, connect-src limited to the wiki (plus a backend widget's registered origin). An unregistered tag renders as nothing for readers; pushing a README with one gets a WIDGET_TAG_UNREGISTERED hint.

Data files: pass src as an absolute path on the wiki, usually your own page's render route (/OWNER/SLUG/render/FILE.json). Relative paths resolve against the widget frame's route and will not find your file.

How scripts are served (read this before curling the raw URLs)

Readers' frames never load the script URLs above directly: they load /widget-script/<name>.js, a registry-gated route that serves only reviewed scripts with a JavaScript MIME, read straight from the page repo. So the host page's visibility does not matter, and the raw URL 404ing for anonymous callers is expected: in this file it is the repo pointer the route resolves, not the URL readers fetch.

What belongs here (read before proposing a widget)

The registry is for generic widgets: one script that many pages reuse, each page passing its own data through attributes or a src file. A pinout, a table, a stock line and a video player all qualify: none of them knows which page it is on.

A tool built for one project does not belong here, however polished. Examples are an explorer for one board's circuit, a simulator of one design, or a calculator for one part: its data lives in the script, and only its own page can use it. Make it that page's readme.html instead, with its JS and CSS inlined, so the tool is the page (it replaces README.md on the page). See the wiki-readme-html skill in adom/adom-wiki-skillpack.

A test for a proposed entry: could two unrelated pages each use it with their own data? If not, it is a readme.html, not a widget.

Registering a widget

Append an entry to widgets.json:

{ "name": "adom-example", "mode": "frontend",
  "script": "https://wiki.adom.inc/OWNER/SLUG/render/widget.js",
  "element": "adom-example", "attrs": ["src"] }

• name: the markdown tag (slug-safe, max 32 chars)
• mode: frontend (wiki-served script) or backend (adds origin)
• script: https URL of the script that defines the custom element
• element: the dashed custom-element name the script defines
• attrs: allowlist of attributes the tag may set (escaped, length-capped); anything else in a tag is dropped
• origin (backend only): the PUBLIC https origin the frame's connect-src widens to; the widget_connect rules apply (no IP literals, loopback, or private TLDs)
• height: auto (default, frames self-report via readme-height) or a fixed pixel number

Registry caps: 32 widgets, 12 attrs each. A malformed entry is dropped, never breaks rendering.

Current widgets

Five load from adom/component-widgets and take a JSON src; adom-stock and adom-video load from this page (adom-video takes video, not src: the wiki inlines a src file into the frame); adom-symbol-variants loads from adom/adom-symbol and takes a component page.json src: