2.3 KiB
markup, title, description
| markup | title | description |
|---|---|---|
| occlusion | view and the user docs site | Local browse and static export from the interpreter |
main
| 返回 | 类型 | 说明 |
|---|---|---|
| result | any | None; execute this page's documented steps in order and observe their output or stated effects |
Version 2.6.0 keeps action descriptions in the sentence and moves their implementation to side notes. Empty parentheses explicitly mark missing logic. Multiple actions and returns keep their original prose, while ordinary links remain navigation. On compact screens, native disclosures keep the implementation readable even without JavaScript.
Executable knowledge now presents inputs, returns, effects, dependencies and separate verification facts. Technical identities and digests stay folded. Source explanations are distinct from captured results; a pure effect summary or linked source is not proof that a program ran or its content was verified.
The reader introduced in 2.5.1: marqdo view and view output share a warm paper reader with a new
Marqdo logo, serif document text, botanical ornaments, navigation, search and a
floating action toolbar. Wide screens place real execution notes in the margins;
compact screens keep them below the corresponding paragraph. Click a note to
inspect its full captured value. Call and loop frame selectors remain available.
Static exports embed decorations, KaTeX and math fonts for offline reading. The play button runs the document in live view; static pages retain their captured results and explain how to start a live view. Ordinary document reruns update prose, bindings and notes from the same execution capture.
Annotations follow the exact source span across calls and loop iterations. Flowing curves and staggered margin notes avoid source text and neighboring connections. The floating toolbar labels its actions: refresh, settings, run, clear and more.
Local: marqdo view public
Static export: marqdo view output public -o public
Browse Structure keeps narration, highlights executable markers, and attaches
run results (values, taken branch arms, call/loop frames). The same render path
builds this user docs site; CI publishes to gh-pages.
We now [Display this step's result](> print text="Docs site: generated by the Marqdo interpreter, not hand-written HTML.").