Showcase
Documentation that keeps its provenance
A documentation page is prose plus evidence: callouts that keep the quick answer close, listings that carry their filename, asides that stay out of the way until asked for, citations a reader can check. Every one of those is an element, not a plugin — and each one is also a record an extractor can quote back.
The document
The collapsed note teases ten words and expands on click; the listing gets copy and wrap controls with line 2 marked; the aside occludes its highlight in quiz views; the citation previews on hover with a backlink.
documentation example
Render view: this block wires to the SemText runtime bundle in the full example viewer (port-reference lane) — the source beside it is the same file, byte for byte.
Why this works
-
sem-codekeeps its source verbatim — extraction returns the listing byte-identical, so a model can quote the config, not a rendering of it. -
sem-referencesmints nothing: the numbering is CSS, the citation is an attribute, and the record survives scripts-off. - Every hide rule is gated on the script having run — with no JavaScript the note is open, the aside is visible, and the document reads whole.
Elements used: sem-note,
sem-code,
sem-details,
sem-references. Their contracts live
on
the reference pages
.