Push hints: suggest ::adom-video for raw <video> tags, and flag adom-video embeds that skip available captions

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. Read this first before publishing or installing.

Overview Files Skills Discover Packages Releases Dependencies Issues8 Breadcrumbs Pull Requests Activity

Closed feature request

John Lauer · 7d ago ·closed by Colby Knox

Ask. Two push-time hints so an AI that embeds a video reaches for the ::adom-video widget and ships captions with it.

README_VIDEO_TAG when a pushed README contains a raw <video>. Suggest ::adom-video{video="/OWNER/SLUG/render/PATH.mp4" poster=... captions=... chapters=...}: YouTube-style player (every YouTube shortcut, hold for 2x, frame step, chapters on the bar). Raw <video> also overflows the column without a width (#205), and can't seek on /render/ today (#225).
VIDEO_NO_CAPTIONS when an ::adom-video tag has neither captions= nor a src= manifest, and the page repo has a .vtt / .srt next to the video (same stem). Name the file in the hint. Even with no captions file, a one-line hint helps: "narrated with adom-tts? gang-takes writes the .vtt for free".

Why. Many of our videos are narrated by adom-tts, so the exact caption text and timing already exist. gang-takes (adom/adom-video-post 1.0.9) now writes final.vtt, final.chapters.json and a ready ::adom-video embed line (plus a private-page manifest with --wiki-path). The skills say so (demo-video-publishing 1.2.3, gang-takes, adom-tts), but a hint at push time is what reaches an AI that never loaded those skills.

Detail for hint 2. For a private page the right form is ::adom-video{src="/OWNER/SLUG/render/PATH.video.json"}. The widget frame's fetch carries no login, so captions/chapters files only load on public pages. A manifest gets inlined by the server and works everywhere.

1 Reply

Colby Knox · 7d ago

Both hints are on prod (715c9e7):

README_VIDEO_TAG (info): a pushed README (root or folder) with a raw <video> gets the ::adom-video{video="/OWNER/SLUG/render/PATH"} line, with the source rewritten to the render route (relative and ../ sources resolve from the README's folder). On a private page the action names the .video.json manifest form. It fires only while adom-video is registered.
VIDEO_NO_CAPTIONS: an ::adom-video with neither captions= nor src=. When a .vtt/.srt with the same stem sits next to the video (in the push or already in the repo), it's a warning naming the file and the captions="..." attribute to add (.vtt preferred), or the manifest form on a private page. With no file it's an info line pointing at gang-takes.

Fenced code blocks and inline code never trigger either, so docs that show the syntax stay quiet. Both codes are in docs/hint-codes.md. Closing.