@lincyaw/skills 1.0.0-rc.16 → 1.0.0-rc.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +2 -2
- package/skills/index.json +5 -5
- package/skills/presmium-animate/SKILL.md +1 -1
- package/skills/presmium-animate/references/libraries.md +2 -0
- package/skills/presmium-animate/references/team.md +28 -11
- package/skills/presmium-author/SKILL.md +2 -1
- package/skills/presmium-author/references/publishing.md +36 -8
- package/skills/presmium-author/references/writing.md +12 -6
- package/skills/presmium-present/SKILL.md +0 -35
- package/skills/presmium-present/references/classroom.md +0 -64
- package/skills/presmium-present/references/delivery.md +0 -122
- package/skills/presmium-present/references/lecture.md +0 -74
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lincyaw/skills",
|
|
3
|
-
"version": "1.0.0-rc.
|
|
3
|
+
"version": "1.0.0-rc.19",
|
|
4
4
|
"description": "Presmium's bundled authoring, animation, presentation and plugin-development skills for coding agents",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
],
|
|
37
37
|
"dependencies": {
|
|
38
38
|
"jiti": "^2.7.0",
|
|
39
|
-
"@lincyaw/kernel": "1.0.0-rc.
|
|
39
|
+
"@lincyaw/kernel": "1.0.0-rc.19"
|
|
40
40
|
},
|
|
41
41
|
"presmium": {
|
|
42
42
|
"skills": [
|
package/skills/index.json
CHANGED
|
@@ -12,8 +12,8 @@
|
|
|
12
12
|
"references/publishing.md",
|
|
13
13
|
"references/writing.md"
|
|
14
14
|
],
|
|
15
|
-
"version": "1.0.0-rc.
|
|
16
|
-
"hash": "
|
|
15
|
+
"version": "1.0.0-rc.19",
|
|
16
|
+
"hash": "4c0c9574d99da410706c0d41108cb3d9ca067446b77759d59b514a95f0841f59"
|
|
17
17
|
},
|
|
18
18
|
{
|
|
19
19
|
"name": "presmium-animate",
|
|
@@ -538,8 +538,8 @@
|
|
|
538
538
|
"references/team.md",
|
|
539
539
|
"references/timeline.md"
|
|
540
540
|
],
|
|
541
|
-
"version": "1.0.0-rc.
|
|
542
|
-
"hash": "
|
|
541
|
+
"version": "1.0.0-rc.19",
|
|
542
|
+
"hash": "ed13f5d387791909866a521e58e7a8695cd94f8d7de96a22af006f398beff94a"
|
|
543
543
|
},
|
|
544
544
|
{
|
|
545
545
|
"name": "presmium-develop",
|
|
@@ -549,7 +549,7 @@
|
|
|
549
549
|
"references/plugin.md",
|
|
550
550
|
"references/testing.md"
|
|
551
551
|
],
|
|
552
|
-
"version": "1.0.0-rc.
|
|
552
|
+
"version": "1.0.0-rc.19",
|
|
553
553
|
"hash": "9b3cab9683b45f11c631a19f916639ffb4c0f74c054c14baee24aa5655a35de4"
|
|
554
554
|
}
|
|
555
555
|
]
|
|
@@ -27,7 +27,7 @@ A teaching segment, an explainer or paper video, a promo, a product demo and a d
|
|
|
27
27
|
|
|
28
28
|
[Story](references/story.md) is the process, each stage ending in a check: brief, thesis, central picture, three storylines for the person to pick, a storyboard of rest frames with what carries each boundary, the script, an animatic the person approves, motion, review against the spec and with cold viewers. [Storyboards](references/storyboards.md) has filled-in examples for popular science, papers, courses, data stories and products; [Scenarios](references/scenarios.md) the usual pictures for each subject.
|
|
29
29
|
|
|
30
|
-
A piece too large for one agent is made from one storyboard file every agent reads, with a term table, shared scene modules that only the coordinator changes, edits through the MCP author actions, review rounds appended to the storyboard and a cold read by a fresh agent: [Team](references/team.md).
|
|
30
|
+
A piece too large for one agent is made from one storyboard file every agent reads, with a term table that gives each term its definition and first page, shared scene modules that only the coordinator changes, edits through the MCP author actions, a reading of its own words every agent does against the storyboard, review rounds appended to the storyboard and a cold read by a fresh agent in three passes: [Team](references/team.md).
|
|
31
31
|
|
|
32
32
|
## 5. Motion, rhythm and sound
|
|
33
33
|
|
|
@@ -16,6 +16,7 @@ A scene file default-exports one call to a function from `@lincyaw/addon-motion/
|
|
|
16
16
|
| `total` | Their sum, the length of the timeline in milliseconds |
|
|
17
17
|
| `width`, `height` | The layout size of `root` in CSS pixels before ancestor transforms (including slide scaling) when the scene is built |
|
|
18
18
|
| `color(name)` | A design-system color as `rgb()`/`rgba()`, such as `color('accent')` (names in "Rules for every library" below) |
|
|
19
|
+
| `parameters`, `state` | The block's parameters and the current step's declared state, read live. A scene whose timeline covers every step reads neither while it builds ("Build once" below) |
|
|
19
20
|
| the library | `gsap` and `plugins`; `anime`; `motion`; `d3`; `THREE`, `renderer` and `addons`; `React` and `remotion` |
|
|
20
21
|
|
|
21
22
|
Each library counts time in its own unit: GSAP and Motion in seconds (`at(k) / 1000`), Anime.js, D3, Three.js and `defineScene` in milliseconds, Remotion in frames.
|
|
@@ -35,6 +36,7 @@ Each library counts time in its own unit: GSAP and Motion in seconds (`at(k) / 1
|
|
|
35
36
|
- **Pictures** are `<img>` elements (a file in the document's `public/` or a URL): the viewer waits for every `<img>` in the scene and for the fonts before the first frame, so an export opens on the picture. A CSS background image or a picture drawn on a canvas is not waited for; a Three.js scene loads its textures in an async build.
|
|
36
37
|
- **Styles:** `frame()` (`gallery/lengths/scenes/kit/frame.ts`) puts the scene's CSS in `@scope`, so two scenes on a page can both style `.card`; a `<style>` written by hand is page-wide. Inside `@scope` a selector matches only below the frame's root. `cqw`/`cqh` inside an element that is itself a size container are that element's units, not the frame's. The page gives every `svg` `max-width: 100%`, which squashes an SVG placed inside a zero-size anchor (a label or icon pinned at a point): give such an SVG `max-width: none`.
|
|
37
38
|
- **Shared modules.** A scene imports other project files with relative `.ts` imports, so the scenes of one piece can share a kit (the frame, the type scale, the colour roles) and a module that draws the central picture and holds the example data: every page then draws the same picture at the same place from the same numbers (`gallery/lengths/scenes/kit/` is such a kit). Changing a shared module changes every page that imports it, so one person owns it ([Team](team.md)). Prefix its class names (`.sm-mark--ok`, not `.ok`): a scene's own `.ok` would take the shared styles, and a tween on a bare selector colours every matching mark on the board. Give it selector functions (`sel.slot(id, i)`) and coordinate functions (`slotCenter(id, i)`) so that pages don't compute positions that break when the shared drawing is resized.
|
|
39
|
+
- **Build once.** The reading page builds a scene when it comes within a screen of the window, while the page is idle (slides build theirs at once), and keeps it from step to step. Reading `state`, or a parameter that changes from step to step, while building makes the scene build again at every step that changes it, and the whole build then stops the page as the reader arrives; read them where the frame is drawn (`seek` in `defineScene`), or not at all when the timeline already covers every step. A build that sets many layout properties in `cqw`/`cqh` makes the browser work out styles once for each: keep a long piece's build to about a tenth of a second (Performance panel, or the long tasks while scrolling the reading page).
|
|
38
40
|
- **A list that makes steps** (clicks, messages, screens) needs as many declared states as items; nothing checks the two agree.
|
|
39
41
|
- **Seeking a one-state scene:** its reading view shows no step buttons (they appear only with more than one state); check seeking with the scrubber (`.pm-scene__scrub`).
|
|
40
42
|
|
|
@@ -16,8 +16,8 @@ One file at the project's root, `storyboard.md`, that every agent reads before i
|
|
|
16
16
|
|
|
17
17
|
**D. Names, colours and space.**
|
|
18
18
|
|
|
19
|
-
- **The term table**: every concept, its one name, the synonyms not to use, and the
|
|
20
|
-
- **The register**: titles, labels, legends, metric names and narration in the formal written words of the audience's field; only a character's quoted speech in a bubble keeps colloquial words. A metaphor system (a game, a court) is mapped term by term on one page; the other pages use the field's own words.
|
|
19
|
+
- **The term table**: every concept, its one name, the synonyms and calques not to use, the page and step that introduce it, and the sentence that defines it there (`presmium-author/references/writing.md`, section 2). A term appears nowhere before that step, and a page title's terms are defined in the page's first step. Two roles that could be confused (the agent drafting the material and the agent under test) get two names, two colours and two icons.
|
|
20
|
+
- **The register**: titles, labels, legends, metric names and narration in the formal written words of the audience's field, its own terms rather than calques (对照组, not 臂, for an experiment's arm); only a character's quoted speech in a bubble keeps colloquial words. A metaphor system (a game, a court) is mapped term by term on one page; the other pages use the field's own words.
|
|
21
21
|
- **Colours**: one colour, one meaning, as a table of roles (truth, wrong, the user, the agent under test) each mapped to a design token in the shared kit, through `color(name)` or `var(--pm-color-<name>)`, never a raw hex.
|
|
22
22
|
- **Space**: one convention, such as left for upstream, input and before, right for downstream, output and after.
|
|
23
23
|
|
|
@@ -36,10 +36,12 @@ One file at the project's root, `storyboard.md`, that every agent reads before i
|
|
|
36
36
|
11. The whole 16:9 frame is used; captions are an overlay that can be off, so no band is kept for them.
|
|
37
37
|
12. Colours only from D, type sizes only from the kit's scale.
|
|
38
38
|
13. The pitfalls in [Libraries](libraries.md), and every new one the coordinator forwards.
|
|
39
|
+
14. Information: no sentence that defends against a reading nobody would make, no position set up only to be rejected, no list of what the piece does not show (`presmium-author/references/writing.md`, section 2). A negation stays when it states an advantage, a condition, or a position someone holds, named.
|
|
40
|
+
15. A term's first mention defines it, with D's sentence; on a `scrolly` page that is in the narration.
|
|
39
41
|
|
|
40
42
|
**F. Files and workflow**: who owns which file (section 2), how the document is changed (section 3), the checks, the captures and the report (section 4).
|
|
41
43
|
|
|
42
|
-
**G. Pages.** The page order, grouped into parts, with a page that maps out the parts before the first one. Per page: its key (also the scene file's name), a title that states the page's claim (with a length limit), the concepts it introduces, and a step table:
|
|
44
|
+
**G. Pages.** The page order, grouped into parts, with a page that maps out the parts before the first one. Per page: its key (also the scene file's name), a title that states the page's claim (with a length limit), the earlier claims it rests on, the concepts it introduces with their definitions from D, and a step table:
|
|
43
45
|
|
|
44
46
|
| Step | Rest frame and motion | Introduces (each new concept, and the motion that brings it in) | Narration points |
|
|
45
47
|
|---|---|---|---|
|
|
@@ -73,16 +75,18 @@ There is one `lecture.json`, so writers must not overwrite each other.
|
|
|
73
75
|
|
|
74
76
|
An agent goes through these after every change, on its own pages only:
|
|
75
77
|
|
|
76
|
-
1. **Check.** `check_document`, then `get_diagnostics`; fix the problems on these pages. A scene whose code doesn't bundle (a syntax error, a missing module) is reported by `check_document` and `presmium check` as a `presmium.preview.code` error with its file and line; it fails alone, so the other pages still preview and present, and its own page shows the failure (the capture's `problems` say why). Fix it before anything else.
|
|
77
|
-
2. **
|
|
78
|
-
3. **
|
|
79
|
-
4. **
|
|
78
|
+
1. **Check the document.** `check_document`, then `get_diagnostics`; fix the problems on these pages. A scene whose code doesn't bundle (a syntax error, a missing module) is reported by `check_document` and `presmium check` as a `presmium.preview.code` error with its file and line; it fails alone, so the other pages still preview and present, and its own page shows the failure (the capture's `problems` say why). Fix it before anything else.
|
|
79
|
+
2. **Reread the words.** Read your pages' narration, titles and on-screen words in order, as someone who has seen only the pages before them, against the storyboard: is each term's first mention its definition from D, and does no term appear before that step? Does any sentence defend against a reading nobody would make, set up a position nobody holds, or list what the piece does not show (E.14)? Is any word a banned synonym or a calque? Does each step's claim follow from what earlier pages stated, without contradicting them? Rewrite what fails; a sentence kept on purpose goes in the report with its reason. This is a reading, not a search: a marker word found by searching is only a candidate, and the sentence in its place decides.
|
|
80
|
+
3. **Look at every step.** `capture_slides` on each page returns every step's rest frame (12 pictures a call; name `steps` for a longer page). Each must read in 3 seconds, with nothing overlapping or cut off; `measure` with a CSS selector gives the boxes of elements when an overlap is hard to see. Capture again with `arrive: 'backward'` and compare: going back must show the same frame. When the reading page matters, `capture_reading` at 1280 and 390. Change and capture again until every frame passes.
|
|
81
|
+
4. **Check the motion.** Rest frames don't show it. Capture `at` moments inside the steps where something moves, and read the timeline: every move has a reason that means something (a cause, the same object, things converging); delete the moves that have none.
|
|
82
|
+
5. **Report** in this form: for each page, its number of steps and one line describing each rest frame; the picture files; the check result; the sentences kept after rereading the words, with their reasons; problems found in shared modules; where the page departs from the storyboard and why; what isn't done or isn't good enough.
|
|
80
83
|
|
|
81
84
|
## 5. The coordinator during production
|
|
82
85
|
|
|
83
86
|
- Dispatch each agent with the storyboard's path, its pages and files, and the reading list of E.1.
|
|
84
87
|
- Read every report and look at its pictures. Settle a difference between pages (one part drawn two ways, one thing named two ways) at once: decide, write it into the storyboard, tell the agents concerned.
|
|
85
88
|
- Forward a pitfall one agent hit to every agent still working, at once; finding it nine times costs more.
|
|
89
|
+
- After each batch of reports, read the narration of the whole document in order for terms that one page uses before another page defines them: such a term belongs to neither agent alone. Settle it in the term table and tell both.
|
|
86
90
|
- When every page is done, run the cold read (section 7) before the author sees the piece.
|
|
87
91
|
|
|
88
92
|
## 6. Review rounds
|
|
@@ -91,7 +95,7 @@ Each review, the cold read and then the author's, ends in a new section at the e
|
|
|
91
95
|
|
|
92
96
|
Decisions about the subject itself (a rule of the method, what counts as a cost) belong to the author: ask, don't settle them in a convention.
|
|
93
97
|
|
|
94
|
-
Before the author sees a round, sweep for terms: search the narration and text in `lecture.json` and the on-screen words in `scenes/*.ts` for every banned synonym in the term table, and for the colloquial words the register rules out. A hit is renamed, not explained.
|
|
98
|
+
Before the author sees a round, sweep for terms: search the narration and text in `lecture.json` and the on-screen words in `scenes/*.ts` for every banned synonym and calque in the term table, and for the colloquial words the register rules out. A hit is renamed, not explained. Whether a first mention defines its term, whether a sentence carries information and whether the argument holds are judged by reading, in the cold read's third pass (section 7), not by a search.
|
|
95
99
|
|
|
96
100
|
What the explainer's two rounds had to add, usable as a checklist for the first version:
|
|
97
101
|
|
|
@@ -104,9 +108,11 @@ What the explainer's two rounds had to add, usable as a checklist for the first
|
|
|
104
108
|
|
|
105
109
|
The lessons: the term table and the register belong in the first version (D), and "introduce, then name, then use" belongs in every step table, as its own column.
|
|
106
110
|
|
|
111
|
+
A second explainer (24 pages, eight agents) added three rules in the middle of production, each at the cost of a message to every agent and a rewrite of finished pages: the information rule (E.14), definitions at first mention (D, E.15) and calques in the term table. Its review also had to read the argument as a chain (section 7, third pass): a background page said random reading cannot tell how much was missed, while the method's own bound on the misses came from uniform reading. These are in the outline above, so a first version starts with them.
|
|
112
|
+
|
|
107
113
|
## 7. The cold read
|
|
108
114
|
|
|
109
|
-
A fresh agent that took no part sees only the pictures and the narration, in order, and reports what a first-time viewer gets. It finds what the makers can't see: contradictions between pages, one word with two meanings, names that drift, concepts used before they were introduced, elements nobody explained. In the explainer it found three problems that blocked the main line, more than twenty concepts left unclear and a dozen flaws in pictures, most of which the agents' own page-by-page checks had missed.
|
|
115
|
+
A fresh agent that took no part sees only the pictures and the narration, in order, and reports what a first-time viewer gets. It finds what the makers can't see: contradictions between pages, one word with two meanings, names that drift, concepts used before they were introduced or never defined, sentences that carry nothing, elements nobody explained. In the explainer it found three problems that blocked the main line, more than twenty concepts left unclear and a dozen flaws in pictures, most of which the agents' own page-by-page checks had missed.
|
|
110
116
|
|
|
111
117
|
**When**: after every round of production or fixes, before the author reviews. A new reviewer each round: one that saw the last version already knows the answers.
|
|
112
118
|
|
|
@@ -150,10 +156,21 @@ Check the wording once more, still changing no files:
|
|
|
150
156
|
Add these to the problem list as P0, P1 or P2.
|
|
151
157
|
```
|
|
152
158
|
|
|
159
|
+
**Third pass: definitions, information and the argument**, sent to the same reviewer after the second:
|
|
160
|
+
|
|
161
|
+
```
|
|
162
|
+
One more pass, still changing no files:
|
|
163
|
+
1. The argument: write each page's claim in one sentence and the earlier pages it rests on. Where does a later page contradict, or quietly drop, what an earlier page stated? Where is a claim made without the step, picture or number that supports it?
|
|
164
|
+
2. Definitions: for each term, the first picture where it appears. Does that step's narration say what it is? List the terms used before they were defined and those never defined.
|
|
165
|
+
3. Sentences that carry nothing: which sentences defend against a reading nobody would make (does not mean, only shows, cannot tell), set up a position nobody holds in order to reject it, or list what the piece does not show? For each, say whether to delete it or to narrow the earlier claim instead.
|
|
166
|
+
4. Calques: which terms are word-for-word translations that people in <the audience's field> would not say? Give the field's own word.
|
|
167
|
+
Add these to the problem list; a contradiction in the argument is a P0.
|
|
168
|
+
```
|
|
169
|
+
|
|
153
170
|
**Use the report:**
|
|
154
171
|
|
|
155
|
-
1. A P0 is usually a contradiction or a role ambiguity: decide one statement for the whole piece, write it into the storyboard (H) and send it to the pages concerned.
|
|
172
|
+
1. A P0 is usually a contradiction or a role ambiguity: decide one statement for the whole piece, write it into the storyboard (H) and send it to the pages concerned. A contradiction in the argument is corrected where the wrong statement is made, usually the earlier page.
|
|
156
173
|
2. A problem with the method itself, such as a rule whose reason no longer holds, goes to the author; don't decide it.
|
|
157
|
-
3. The wording problems become one term table in the storyboard, which every page follows.
|
|
174
|
+
3. The wording problems become one term table in the storyboard, which every page follows; definitions and calques go into its columns, which the next round's agents and reviewer read against.
|
|
158
175
|
4. Fixes go to the agents that made the pages.
|
|
159
176
|
5. After the fixes, capture everything again and give it to a new reviewer.
|
|
@@ -30,13 +30,14 @@ Terms used throughout:
|
|
|
30
30
|
| Make one large piece with several agents in parallel | `presmium-animate/references/team.md` |
|
|
31
31
|
| Generate voiceover, choose voices, set captions, record or make the video | [Lecture production](references/lecture.md) |
|
|
32
32
|
| Build a site, slides, PDF, PowerPoint, notebook, translation or student version; prepare offline | [Publishing](references/publishing.md) |
|
|
33
|
+
| Write or restyle a site's homepage (`site/home.json`), choose its theme | [Publishing, Write the homepage](references/publishing.md#write-the-homepage) |
|
|
33
34
|
| Run a class with quizzes, polls and students following along | [Classroom](references/classroom.md) |
|
|
34
35
|
| Details of every studio and MCP action: conflicts, approvals, audio and image import, transcription | [Assistance](references/assistance.md) |
|
|
35
36
|
| Implement a component or service | `presmium-develop` |
|
|
36
37
|
|
|
37
38
|
## Writing in one paragraph
|
|
38
39
|
|
|
39
|
-
Each page has one idea and two versions. The reading version is written like a book: formal written language, Chinese in Chinese word order and English in English word order, every sentence carrying information. The presentation version shows a claim as its heading, keywords and pictures, and moves with steps; its explanation is the narration, a separate spoken script rather than the reading text read aloud. Both use one name per concept throughout, and formal words of the audience's field in titles, labels and narration; a concept is shown before it is named and used. Shared figures, animations and code are written once; reading paragraphs are limited to `["web", "notebook"]` (or `["web"]` when the document doesn't build a notebook), slide keywords to `["slides", "lecture"]`. [Writing](references/writing.md) has the rules and the review.
|
|
40
|
+
Each page has one idea and two versions. The reading version is written like a book: formal written language, Chinese in Chinese word order and English in English word order, every sentence carrying information. The presentation version shows a claim as its heading, keywords and pictures, and moves with steps; its explanation is the narration, a separate spoken script rather than the reading text read aloud. Both use one name per concept throughout, and formal words of the audience's field (its own terms, not calques) in titles, labels and narration; a concept is shown before it is named and used, and its first mention defines it. Neither version defends against a reading nobody would make. Shared figures, animations and code are written once; reading paragraphs are limited to `["web", "notebook"]` (or `["web"]` when the document doesn't build a notebook), slide keywords to `["slides", "lecture"]`. [Writing](references/writing.md) has the rules and the review.
|
|
40
41
|
|
|
41
42
|
## Work through the tools
|
|
42
43
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Publishing, export and offline
|
|
2
2
|
|
|
3
|
-
`lecture.json` is the only editable source; every output is derived from it. A workspace configuration normally lists `documents: ['*/lecture.json']`; an independent site homepage is configured separately under `site.landing` and is not a teaching document. Ordinary README Markdown is not a document entry. Never publish credentials or operator settings in document JSON.
|
|
3
|
+
`lecture.json` is the only editable source; every output is derived from it. A workspace configuration normally lists `documents: ['*/lecture.json']`; an independent site homepage is configured separately under `site.landing` and is not a teaching document. Ordinary README Markdown is not a document entry. To bring a folder of Markdown notes into a workspace, `presmium import notes --out . --exclude raw` writes one `lecture.json` per note (a page per level-1 and level-2 heading, `[[wikilinks]]` resolved by file name or alias, linked local files copied into the document's `attachments/`) and prints the `documents` patterns that list them; the generated documents are then the source to edit, or the notes stay the source and the import runs before every build. Never publish credentials or operator settings in document JSON.
|
|
4
4
|
|
|
5
5
|
Pick the build from what the teacher hands out, and build only the relevant document and form during routine work. Run document commands in the document folder. Before building, read `metadata.renderers`: it lists the forms (`web`, `slides`, `notebook`, `lecture`) with their options, among them `base`, the URL path a form's site is served at (such as `/course/week1/`). When `base` is already set, keep it and the hosting the teacher already uses. Plugin document settings belong in `metadata.presmium`.
|
|
6
6
|
|
|
@@ -132,20 +132,48 @@ pnpm serve
|
|
|
132
132
|
|
|
133
133
|
The scaffold contains an independent homepage at `site/home.json`, a teaching document at `intro/lecture.json`, and `presmium.workspace.yaml`. `site.landing: { source: './site/home.json' }` selects the homepage file; a `SiteLandingPage` object can also be written directly in `site.landing`. The homepage uses its own `schemaVersion: 1`, `title`, optional description/hero, and required `sections` array. It is a site page, without teaching steps, narrations or production settings. Do not wrap independent homepage content in a teaching document or add it to `documents`.
|
|
134
134
|
|
|
135
|
+
### Write the homepage
|
|
136
|
+
|
|
137
|
+
The built-in themes lay a JSON homepage out the way blog and documentation sites lay out their front pages: a centred hero, then each section under a centred title, cards in a grid of equal widths centred as a group, running text in a reading column aligned to the start. The layout is the theme's; the homepage file decides only the words, their order and their length, and short words are what make the page look finished.
|
|
138
|
+
|
|
139
|
+
First decide whether the site needs a hero at all. A site of a few documents whose name in the header already says what it is (one explainer, a set of notes) needs none: leave `hero` out and the page starts at the documents. The file's `title` still names the page in the browser tab. Write a hero when the site has more to say than its name: a course with a term and an audience, a product. Then write it like this:
|
|
140
|
+
|
|
141
|
+
| Field | Write |
|
|
142
|
+
|---|---|
|
|
143
|
+
| `hero.eyebrow` | What the site is, in a few words: the course and term, or the topic (at most 12 Chinese characters or 5 English words). Leave it out rather than repeat the title. |
|
|
144
|
+
| `hero.title` | The site's name or its promise, on one line on a desktop: at most 16 Chinese characters or 8 English words, no closing punctuation. |
|
|
145
|
+
| `hero.description` | One or two sentences, at most 60 Chinese characters or 30 English words: who it is for and what they get. Not a list of features. |
|
|
146
|
+
| `hero.actions` | One `primary` action to the first thing to read (the first document's `/dir/`), and at most one `secondary` (a section anchor such as `#features`, or `documents.html`). A verb and its object: 开始阅读, 浏览课程. |
|
|
147
|
+
| `hero.image` | Only a picture of the content itself (a page, a slide, a diagram), shown under the words at most 24rem high; a transparent PNG or SVG, always with `imageAlt`. No stock photos. |
|
|
148
|
+
|
|
149
|
+
Sections, two to four, usually in this order: `features` (what a reader gets), `documents` (where to start), optionally `text` or `media`, and a closing `cta`. Give each a `title` of at most 10 Chinese characters or 5 English words, and a `description` only when one sentence adds something.
|
|
150
|
+
|
|
151
|
+
- `features`: three items (or six), written in parallel: a title of at most 8 Chinese characters or 4 English words, and a description of one or two lines on the card (at most 40 Chinese characters or 20 English words). Items of about the same length keep the cards the same height.
|
|
152
|
+
- `documents`: always include one, so that readers reach the content. The theme draws the list (`course`: one numbered column; `docs`: cards; `showcase`: large cards). Each card shows a document's `metadata.title`, `metadata.description` (write one sentence) and `metadata.tags` (one or two), so write those in every `lecture.json`.
|
|
153
|
+
- `text`: at most three short paragraphs; anything longer is a document.
|
|
154
|
+
- `media`: one image or video that shows the work, with `alt`, and `captions` for speech.
|
|
155
|
+
- `cta`: last, a short question or invitation and one action, usually the hero's primary action again.
|
|
156
|
+
|
|
157
|
+
`site.nav` in the workspace configuration holds only site-wide destinations: another site, the code repository, an about page. Do not add an entry per document; readers reach documents from the homepage list and the contents beside every document page, and a site without `nav` shows only its name and tools in the header.
|
|
158
|
+
|
|
159
|
+
No emoji, decorative symbols, exclamation marks, HTML or CSS in any field. Then look at the page in `presmium serve` at desktop width and below 768 px, light and dark: the hero title fits one line on the desktop, the lead runs two lines at most, and the feature cards are the same height.
|
|
160
|
+
|
|
135
161
|
For a freely designed homepage, use `site.landing: { template: './site/home.html' }`. Vite builds the HTML entry and its CSS, JavaScript and local assets; it is not a React/viewer-shell plugin. The injected `script#presmium-site-data` contains only `schemaVersion`, `title`, `base`, `lang`, and public `documents` (`id`, `title`, `href`, optional `description`, `lang`, `tags`, `pages`). Read its JSON and use published `href` values; create DOM nodes with text content for document titles. Do not insert document IR, diagnostics, configuration or operator settings into template data. `source` and `template` are exclusive. A served template rebuilds on page refresh; there is no template hot update channel.
|
|
136
162
|
|
|
137
163
|
Resolve JSON page media relative to that JSON file, inline media relative to the workspace configuration, and HTML assets relative to the HTML entry. Workspace `public/` files are published at the site root. Rebuild for deployment after changing the homepage.
|
|
138
164
|
|
|
139
165
|
Existing string configuration `site.landing: welcome` remains available when the author intentionally wants a teaching document as the homepage. That directory must belong to `documents`; all its sections appear at the site root and its document URL remains available. Keep `lecture.json` as the only editable content source for that teaching document. Existing `site.home` redirects to a document and cannot be combined with any form of `landing`.
|
|
140
166
|
|
|
141
|
-
In the workspace configuration, `site.theme` selects `course`, `docs` or `showcase`; the renderer defaults to `docs
|
|
167
|
+
In the workspace configuration, `site.theme` selects `course`, `docs` or `showcase`; the renderer defaults to `docs`, while a new `site` scaffold selects `course`. All three share one surface: a cool light grey page (near-black in dark mode) under a translucent header with the site's name and navigation, sans-serif type and pill-shaped buttons. The workspace's theme and brand apply to all documents. `site.params` supports only these parameters:
|
|
142
168
|
|
|
143
|
-
| Parameter | Values |
|
|
144
|
-
|
|
145
|
-
| `accent` | `blue`, `teal`, `violet`, `amber` |
|
|
146
|
-
| `typography` | `reading
|
|
147
|
-
| `contentWidth` | `comfortable`, `wide` |
|
|
148
|
-
| `logo`, `logoAlt` | The logo location and alternative text |
|
|
169
|
+
| Parameter | Values | Default (`docs`, `course` / `showcase`) |
|
|
170
|
+
|---|---|---|
|
|
171
|
+
| `accent` | `blue`, `teal`, `violet`, `amber` | `blue` / `violet` |
|
|
172
|
+
| `typography` | `reading` (serif text), `sans` | `sans` / `sans` |
|
|
173
|
+
| `contentWidth` | `comfortable`, `wide` | `comfortable` / `wide` |
|
|
174
|
+
| `logo`, `logoAlt` | The logo location and alternative text | none |
|
|
175
|
+
|
|
176
|
+
Leave a parameter out to take the theme's default; a site that names `accent: teal` or `typography: reading` keeps that choice.
|
|
149
177
|
|
|
150
178
|
For a look of its own, `site.theme` names a theme directory (`./theme`) or an installed theme package instead of a built-in id. The directory holds `theme.json`:
|
|
151
179
|
|
|
@@ -15,7 +15,7 @@ Write these down before the first page. When the request doesn't give the audien
|
|
|
15
15
|
- **Core claim**: the one sentence the audience should understand at the end, with its reason: "读完后,读者明白 X,因为看到了 Y". A topic ("讲讲缓存") is not a claim; "第二次取同一本书只要伸手到桌上,所以缓存让重复读取变快" is.
|
|
16
16
|
- **Forms that matter**: which of the reading page, the slides and the lecture video the author will actually hand out (`metadata.renderers` lists what the document builds: `web`, `notebook`, `slides`, `lecture`). Write the versions that are used; don't fill in a version nobody will see.
|
|
17
17
|
- **One idea per page**: list the pages as one sentence each before writing any of them. If a page needs two sentences, it is two pages.
|
|
18
|
-
- **Terms**: a table of the concepts the document uses, each with its one name
|
|
18
|
+
- **Terms**: a table of the concepts the document uses, each with its one name, the synonyms and calques not to use, the page and step where it first appears and the sentence that defines it there (section 2, "Name each concept once"). A document written by several people or agents doesn't stay consistent without it.
|
|
19
19
|
|
|
20
20
|
## 2. The information principle
|
|
21
21
|
|
|
@@ -37,7 +37,7 @@ Search the draft for these markers. Most hits are deleted or rewritten; keep a h
|
|
|
37
37
|
|
|
38
38
|
| Pattern | Markers | Repair |
|
|
39
39
|
|---|---|---|
|
|
40
|
-
| Defending against a misreading nobody had |
|
|
40
|
+
| Defending against a misreading nobody had | 不代表、不意味着、并不是说、不等于、只说明、不能说明、测不出来; this does not mean, we do not claim, only shows | Delete. If the earlier claim really invites the misreading, narrow that claim instead |
|
|
41
41
|
| Strawman contrast | 不是 A 而是 B、并非 A 而是 B; not A but B | When nobody holds A, state B directly. When A is a real, common belief, keep it and say whose belief it is |
|
|
42
42
|
| Narrated history | 起初、后来发现、我们首先尝试; initially, we first tried | Keep only the result |
|
|
43
43
|
| Signpost | 值得注意的是、需要指出的是、不难看出; it is worth noting, note that | Delete the signpost and state the thing |
|
|
@@ -48,6 +48,8 @@ Search the draft for these markers. Most hits are deleted or rewritten; keep a h
|
|
|
48
48
|
|
|
49
49
|
The test for each hit: **would a reader who has read everything up to here plausibly believe what this sentence answers?** If not, the sentence answers a question nobody asked: delete it. Negations that state an advantage ("无需标注", "no retraining") or a condition in a definition are information; keep them.
|
|
50
50
|
|
|
51
|
+
The same pattern comes a page at a time: a closing section on what the results cannot show defends the whole piece. Write what the work answers instead, each question with the measure that answers it; a limit the reader needs is stated once, as a condition of the claim it limits.
|
|
52
|
+
|
|
51
53
|
### Choose the medium
|
|
52
54
|
|
|
53
55
|
When a paragraph has been rewritten three times and still reads heavy, it belongs in another medium: a comparison of three things is a table, a system of parts is a diagram, a process is an animation or a numbered list, a relation between quantities is a formula or a chart. Stop polishing prose in the wrong medium.
|
|
@@ -58,6 +60,7 @@ A second name tells the audience there is a second thing. In a 19-page explainer
|
|
|
58
60
|
|
|
59
61
|
- **One name per concept** across the whole document: titles, labels, legends, narration and reading text. Keep it in the term table (section 1) with the synonyms not to use.
|
|
60
62
|
- **One concept per name.** "Agent" meant both the agent that drafted the material and the agent under test, drawn in the same colour with the same icon, and viewers concluded that the tested agent wrote its own questions. Two roles get two names, and in pictures two colours.
|
|
63
|
+
- **Define a term where it first appears.** The first title, label, line of narration or paragraph that uses a term says what it is, in one sentence; later pages use it without comment. A term appears nowhere before the step that defines it, and a page title's terms are defined in that page's first step. A 24-page storyboard written for eight agents first used the method's own name (搜索) on page 4 and explained it on page 10, and used a score (惊奇度) one page before the page that defined it: a reader of the web page meets each as an unexplained word. On a `scrolly` page the narration is the reading text, so the definition goes in the narration (section 6).
|
|
61
64
|
- **Sweep at the end**: search the narration, the slide text and the words in scenes for every synonym the table rules out. A hit is renamed, not explained.
|
|
62
65
|
|
|
63
66
|
### Formal words in the audience's terms
|
|
@@ -76,6 +79,7 @@ A second name tells the audience there is a second thing. In a 19-page explainer
|
|
|
76
79
|
| 走错的代价:悄悄认定与回溯 (a page title) | 错误结论的代价:静默确认与结论推翻 |
|
|
77
80
|
|
|
78
81
|
- **The audience's own words, one metaphor system.** Use the everyday terms of the audience's field (an operations engineer says 排查, 协查 and 结案), not a vocabulary borrowed from elsewhere. A metaphor that helps (an evaluation as a game, the user as its non-player character) is mapped once, on one page, term by term; the other pages use the field's words. An explainer that mixed the vocabularies of games, courts, Kubernetes and operations left its viewers translating between four.
|
|
82
|
+
- **The field's own words, not calques.** In Chinese, use the term the field already uses in Chinese (an experiment's arm is 对照组, not 臂); keep an English term the field keeps in English (agent, harness); a concept with neither gets a plain name for what it is (a facet becomes 问题定义). A calque reads as translated and leaves the reader to translate it back. Put the calques a draft is tempted by in the term table, as words not to use.
|
|
79
83
|
- **A person is named, not 它.** In Chinese, refer to a person by their role (用户, 值班工程师), never 它, which makes them a thing.
|
|
80
84
|
|
|
81
85
|
## 3. One page, two versions
|
|
@@ -162,9 +166,11 @@ Review from the seat of someone who hasn't seen the document, not from the seat
|
|
|
162
166
|
|
|
163
167
|
1. **Read the reading version alone**, start to end, in the reading preview, with the slides and narration out of mind. Mark every place where a term is undefined, a step of reasoning is missing or a sentence depends on something said only in the narration.
|
|
164
168
|
2. **Watch the presentation with the sound off**: each slide should show its point through the heading and the picture. Then **listen without looking**: the narration should not rely on "这里" or "如图" pointing at nothing.
|
|
165
|
-
3. **Sweep both versions** with the marker table, the term table's banned synonyms and the colloquial words of section 2, and for Chinese, the translationese table of section 4. Include the words inside scenes, which a search of the text blocks misses.
|
|
166
|
-
4. **
|
|
167
|
-
5. **
|
|
168
|
-
6. **
|
|
169
|
+
3. **Sweep both versions** with the marker table, the term table's banned synonyms and calques and the colloquial words of section 2, and for Chinese, the translationese table of section 4. Include the words inside scenes, which a search of the text blocks misses. Each marker hit is judged by the test of section 2, not deleted on sight: a search finds candidates, and reading the sentence in its place decides.
|
|
170
|
+
4. **Read for definitions**, in page order, as someone who has seen only the earlier pages: at each term's first mention, does that sentence say what it is? A term met before its definition, or never defined, is fixed where it first appears.
|
|
171
|
+
5. **Check the structure**: one idea per page, the core claim on the first page and again on the last, every concept introduced before it is used, a method explained before its steps, and no run of slides whose shared arrangement hides a relation their content has (section 5).
|
|
172
|
+
6. **Check the argument as a chain**: write each page's claim in one sentence with the earlier claims it rests on, and read the chain in order. A later page must not contradict or quietly drop an earlier statement: one explainer said that random reading cannot tell how much was missed, while its own method bounded the misses with uniform reading. Correct the earlier statement.
|
|
173
|
+
7. **Ask a fresh reader** (a person, or a subagent given only the built output) to retell the core claim in their own words and to predict what the next page shows. "Clear" is not a pass; a correct retelling is. For a long piece, `presmium-animate/references/team.md` (section 7) has a prompt for a page-by-page cold read, a second pass on names and register, and a third on definitions, information and the argument.
|
|
174
|
+
8. **Validate and preview**: `presmium check <document>`, then the reading page and the presentation of the changed pages. Labels and code must be visible, steps reversible and every page's final step complete.
|
|
169
175
|
|
|
170
176
|
Keep IDs when revising: comments, steps and narration stay attached to their blocks. See [Document format](document.md) for the entities and [Publishing](publishing.md) for the outputs.
|
|
@@ -1,35 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: presmium-present
|
|
3
|
-
description: "Present and deliver a Presmium document, run classroom interaction, export or record it, and manage structured narration, real speech synthesis, subtitles and video playback from lecture.json production settings. 放映、上课、导出、录课、配音、字幕与讲授视频时使用。"
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Presenting and producing a lecture
|
|
7
|
-
|
|
8
|
-
The editable document is `lecture.json`. Reading, slides, notebook and narrated lecture are derived forms. The **lecture** is narrated playback/video, not a second editable source. Keep document editing, compiled presentation and video production separate.
|
|
9
|
-
|
|
10
|
-
| Task | Read |
|
|
11
|
-
|---|---|
|
|
12
|
-
| Present, share or prepare offline outputs | [Delivery](references/delivery.md) |
|
|
13
|
-
| Classroom questions, quizzes and interaction | [Classroom](references/classroom.md) |
|
|
14
|
-
| Narration, voice, captions, recording or video | [Lecture production](references/lecture.md) |
|
|
15
|
-
|
|
16
|
-
Read the document and installed plugin capabilities before operating. Compilation can fail while the document remains saved; identify which source version a displayed snapshot represents. Never use stale audio or a stale generated result as the current document's result.
|
|
17
|
-
|
|
18
|
-
## Run only the requested output
|
|
19
|
-
|
|
20
|
-
```sh
|
|
21
|
-
presmium check lesson --json
|
|
22
|
-
presmium dev lesson
|
|
23
|
-
presmium build lesson --to slides
|
|
24
|
-
presmium build lesson --to lecture
|
|
25
|
-
```
|
|
26
|
-
|
|
27
|
-
Renderers are configured in `metadata.renderers`; document plugins in `metadata.plugins` and document plugin settings in `metadata.presmium`. Operator credentials and provider endpoints remain outside the document. Read the installed renderer's public configuration for actual export support.
|
|
28
|
-
|
|
29
|
-
## Narration and playback rules
|
|
30
|
-
|
|
31
|
-
Steps explicitly reference structured narrations. Voice source and playback timing are owned by `production`. Resolve actual provider voices and supported parameters instead of inventing a catalogue. Changing a voice or script does not synthesize automatically. Explain the target/provider and scope before an explicit paid action.
|
|
32
|
-
|
|
33
|
-
Audition and formal playback share exclusive ownership: starting either stops or pauses the other. Seeking pauses first and reconstructs the selected step state. Cancel a task without deleting valid completed cache entries. Confirm saved/generated results against target document, request and version.
|
|
34
|
-
|
|
35
|
-
Check visible content, captions, step navigation and audio on the actual output. A successful compile alone does not prove playable speech or a working exporter.
|
|
@@ -1,64 +0,0 @@
|
|
|
1
|
-
> Editable source is `lecture.json`; renderer settings are under `metadata.renderers`, steps and narrations are explicit entities, and production timing/voices live only in `production`.
|
|
2
|
-
|
|
3
|
-
# Classroom
|
|
4
|
-
|
|
5
|
-
A classroom lets students scan a QR code, follow the presenter's position on their own device, answer quizzes and polls, submit exercises and ask questions. It has three parts, each on its own address:
|
|
6
|
-
|
|
7
|
-
- the **student site**: a static build of the document for students, served on the class network;
|
|
8
|
-
- the **classroom server** (`presmium-classroom-server`): a small sync server the presenter and all students connect to;
|
|
9
|
-
- the **presenter's page**: the whole document, built with the same classroom server setting, opened by the teacher.
|
|
10
|
-
|
|
11
|
-
Do not run a class from `presmium dev` or `presmium serve`. Their built-in classroom sync is for the teacher rehearsing on this computer; anyone who reaches those services has the teacher's rights and sees the whole document.
|
|
12
|
-
|
|
13
|
-
## Prepare the site and the server
|
|
14
|
-
|
|
15
|
-
1. **Plugins.** List `@lincyaw/addon-session` (joining and following) and `@lincyaw/addon-classroom` (quizzes, polls, questions) in the `metadata.plugins`; add `@lincyaw/addon-exec` when students submit code exercises that are checked. Install each with `pnpm add -D <package>`.
|
|
16
|
-
|
|
17
|
-
2. **Start the classroom server** on a computer in the class network:
|
|
18
|
-
|
|
19
|
-
```sh
|
|
20
|
-
pnpm add -g @lincyaw/classroom-server
|
|
21
|
-
presmium-classroom-server --port 1234 --deck .
|
|
22
|
-
```
|
|
23
|
-
|
|
24
|
-
Run it in the document folder: `--deck` is the folder where archived classrooms are written (default: the current folder). `--port` defaults to 1234 (`0` picks a free one); `--host` limits the address it listens on (default: every interface). It prints the addresses it can be reached at; pick the local-network one (such as `192.168.1.10`), not `localhost`, because student devices reach it there.
|
|
25
|
-
|
|
26
|
-
3. **Point the document at the server.** In `lecture.json` under `metadata.presmium`, with the address printed in step 2:
|
|
27
|
-
|
|
28
|
-
```json
|
|
29
|
-
{ "presmium.session": { "server": "ws://192.168.1.10:1234" } }
|
|
30
|
-
```
|
|
31
|
-
|
|
32
|
-
`metadata.presmium` holds settings per plugin; `presmium.session` is the session plugin's. An `http://` address is turned into `ws://`. The address is written into the build, so rebuild after changing it.
|
|
33
|
-
|
|
34
|
-
4. **Build both versions** with that setting, each into its own folder:
|
|
35
|
-
|
|
36
|
-
```sh
|
|
37
|
-
presmium build --to web --audience student --out dist-student
|
|
38
|
-
presmium build --to web --out dist-full
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
`--audience student` leaves out content marked for teachers only (for example a block with `audience: ["teacher"]`; the markers are explained in `presmium-author/references/publishing.md`, "Content for students"). The two versions keep students at the same section as the presenter by the sections' ids, so keep stable section IDs when you edit between builds.
|
|
42
|
-
|
|
43
|
-
5. **Serve them** as static sites on the class network (commands in [delivery.md](delivery.md), "Give readers a web address"): `dist-student/web` for students, `dist-full/web` for the teacher.
|
|
44
|
-
|
|
45
|
-
**Network and safety.** The classroom server has no TLS and no login: anyone with the join link can join, so run it on the class's own network. A site served over HTTPS needs a `wss://` server address the browsers can reach. Only the browser window that created a classroom can end or archive it, open and close its quizzes, or move its students; everyone else writes only their own answers, questions, votes and submissions.
|
|
46
|
-
|
|
47
|
-
## Run a class
|
|
48
|
-
|
|
49
|
-
1. **Create the classroom.** The teacher opens the full site's address (the local-network address, not `localhost`), clicks **Classroom** in the navigation bar, then **Create classroom** (in the slides form, the classroom is in the presenter window's panel). A join link and a QR code appear. Scan it from a phone or open it in another browser to check that joining works.
|
|
50
|
-
2. **Following.** Students follow the presenter by default: when the teacher moves to another section or step, each student lands at the same place. A student who clicks **Browse alone** moves on their own; **Back to the presenter** resumes following. Check this once with your test student before class. Teacher-only content does not appear on students' screens, because their site was built without it.
|
|
51
|
-
3. **Quizzes.** On a quiz, the teacher clicks **Open answering**; students submit; the correct answer is shown only after the teacher clicks **Close answering**. For an exercise, the teacher sees who passed after students submit. Questions, polls and understanding checks are collected under **Interaction** in the teacher's classroom panel.
|
|
52
|
-
4. **After class.** Click **End classroom**, then **Archive classroom**. The archive is written to `.presmium/classroom/<room>.json` in the server's `--deck` folder; after that nobody can join or write. Personal notes are not archived. The archive is ignored by git by default; back it up separately when it must be kept.
|
|
53
|
-
|
|
54
|
-
A classroom lives in the server's memory: restarting the server before archiving loses its records. If the teacher's window closes by accident, reopen the same address in the same browser and choose **Rejoin classroom <room> as presenter**.
|
|
55
|
-
|
|
56
|
-
## Predictions and AI answers
|
|
57
|
-
|
|
58
|
-
The prediction component asks students to write a prediction before what follows is shown. In the web Document view the student must save a prediction first; in Present and in the slides, the teacher's next step reveals it as usual. When a document uses it, check it on a student device; the teacher's screen does not show the student side.
|
|
59
|
-
|
|
60
|
-
With `@lincyaw/addon-assistant` in `metadata.plugins` and a model set up in the teacher's browser (students need no model key), the teacher can generate an AI answer to a student's question, read it in their own window, and click **Send to the classroom**. Until it is sent, nobody else sees it.
|
|
61
|
-
|
|
62
|
-
## When students cannot join
|
|
63
|
-
|
|
64
|
-
Check separately that a student device opens the student site, and that it connects to the classroom server: the address, the port, and `ws://` for an `http://` site or `wss://` for an `https://` site. After changing the `server` setting: rebuild, restart the static server, and create the classroom again to get a new join link.
|
|
@@ -1,122 +0,0 @@
|
|
|
1
|
-
> Editable source is `lecture.json`; renderer settings are under `metadata.renderers`, steps and narrations are explicit entities, and production timing/voices live only in `production`.
|
|
2
|
-
|
|
3
|
-
# Publishing, export and offline
|
|
4
|
-
|
|
5
|
-
Pick the build from what the teacher hands out. Run every command in the document folder. Before building, read the `metadata.renderers`: it lists the forms (`web`, `slides`, `notebook`, `lecture`) with their options, among them `base`, the URL path a form's site is served at (such as `/course/week1/`). When `base` is already set, the site is meant for that path: keep it and the hosting the teacher already uses.
|
|
6
|
-
|
|
7
|
-
`presmium build` writes into `dist/` (or the folder given with `--out`): one subfolder per form, such as `dist/web/`. Building is not deploying: copy the output to whatever host the teacher chooses.
|
|
8
|
-
|
|
9
|
-
## Give readers a web address
|
|
10
|
-
|
|
11
|
-
```sh
|
|
12
|
-
presmium build --to web
|
|
13
|
-
```
|
|
14
|
-
|
|
15
|
-
When only the web form is built and `base` is not set, `dist/web/` is a site for the root path `/`. To serve it on this computer when the project has no static server yet:
|
|
16
|
-
|
|
17
|
-
```sh
|
|
18
|
-
pnpm add -D sirv-cli
|
|
19
|
-
pnpm exec sirv dist/web --port 8080
|
|
20
|
-
```
|
|
21
|
-
|
|
22
|
-
Open the address the terminal prints; the document's first page appears. Chapter pages have their own HTML files; a document with `metadata.renderers.web.layout: landing` combines all sections into one HTML page. A host needs no single-page-app fallback rule. Restart sirv after every rebuild: the file names change and a running sirv does not see the new ones.
|
|
23
|
-
|
|
24
|
-
**Student version.** Build it into its own folder so nothing from a full build is mixed in, and serve `dist-student/web` instead:
|
|
25
|
-
|
|
26
|
-
```sh
|
|
27
|
-
presmium build --to web --audience student --out dist-student
|
|
28
|
-
```
|
|
29
|
-
|
|
30
|
-
`--audience student` leaves out content marked for teachers only (markers such as `:audience: teacher` are explained in `presmium-author/references/publishing.md`, "Content for students"). Every file written is then scanned for sentences of the left-out content; a hit is reported as `presmium.audience` and means teacher content leaked into the student version through some output; trace and fix it in the source. Then open the student site and look for teacher narration, answers and media.
|
|
31
|
-
|
|
32
|
-
## Publish a themed workspace
|
|
33
|
-
|
|
34
|
-
A website created with `presmium new my-site --type site --theme course` has an independent homepage (`site/home.json`), a teaching document (`intro/lecture.json`), workspace configuration and `.github/workflows/pages.yml`. In that project, use `pnpm install`, `pnpm serve` for local preview, and `pnpm build` to write `dist/web/`.
|
|
35
|
-
|
|
36
|
-
Read the workspace's `site` before changing appearance or hosting. `site.theme` selects `course`, `docs` or `showcase`; `site.params` selects `accent` (`blue`, `teal`, `violet`, `amber`), `typography` (`reading`, `sans`), `contentWidth` (`comfortable`, `wide`), and optional `logo`/`logoAlt`. Preserve a configured `base`. A workspace applies one theme and brand across documents; a document can set `metadata.renderers.web.layout` to `article`, `landing` or `wide`. When building a document by itself, its `metadata.renderers.web` can also select `theme` and `params`.
|
|
37
|
-
|
|
38
|
-
`site.landing: { source: './site/home.json' }` selects an independent homepage; the same site page object may be written inline. Its own title, hero and sections introduce the site without using a teaching-document model. Homepage files are outside `documents`; teaching content still has `lecture.json` as its only editable source.
|
|
39
|
-
|
|
40
|
-
`site.landing: { template: './site/home.html' }` selects a free HTML/CSS/JavaScript homepage instead. Its local assets are built with Vite and its injected `script#presmium-site-data` holds only the public site title, base, language and document collection. Read the JSON and use the published document links. Refresh the page to rebuild a served template; there is no template hot update channel. Build again before deployment.
|
|
41
|
-
|
|
42
|
-
Existing string configuration `site.landing: welcome` intentionally uses all sections of `welcome/lecture.json` at the website root and keeps its document URL and normal chapter pagination. A document's own `metadata.renderers.web.layout: landing` combines its sections into one webpage at that document's address. `site.home` retains redirect behavior and cannot be set together with any form of `landing`.
|
|
43
|
-
|
|
44
|
-
Each translation chooses its own document layout; an omitted layout means `article`, while the workspace's theme stays shared. Restart `pnpm serve` after editing website settings in `presmium.workspace.yaml`, or run `pnpm build` again to export them.
|
|
45
|
-
|
|
46
|
-
For GitHub Pages, the generated workflow reads the deployment base path and publishes `dist/web/`. The repository's Pages source must be GitHub Actions. After deploying, open the real root address and an inner-page direct link, use search, and play the media. Ordinary file links can publish PowerPoint or Word downloads; choosing a theme does not add Office import or an Office previewer.
|
|
47
|
-
|
|
48
|
-
## Hand out the web page and the slides together
|
|
49
|
-
|
|
50
|
-
Built together, with `base` set on neither, the web page is at `/web/` and the slides at `/slides/` of one site. Serve the whole `dist/` folder:
|
|
51
|
-
|
|
52
|
-
```sh
|
|
53
|
-
presmium build --to web,slides
|
|
54
|
-
pnpm exec sirv dist --port 8080
|
|
55
|
-
```
|
|
56
|
-
|
|
57
|
-
Open `<address>/web/` and `<address>/slides/`. The slides are one page (`index.html`); the slide and step are in the address's query (`?slide=<number>&step=<step>`), so a host needs no fallback rule here either.
|
|
58
|
-
|
|
59
|
-
When only the slides are built and `base` is not set, serve `dist/slides` instead (`pnpm exec sirv dist/slides --port 8080`). When the site already lives under a sub-path, serve the output at that path.
|
|
60
|
-
|
|
61
|
-
Each section heading on the web page links to the same place in the slides. When the two are deployed at different addresses, write the slides' real address in the document metadata, then check that a heading link lands on the right slide and step:
|
|
62
|
-
|
|
63
|
-
```json
|
|
64
|
-
{ "presmium.web": { "slidesUrl": "https://example.com/slides/" } }
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
## Export a PDF, images or PowerPoint
|
|
68
|
-
|
|
69
|
-
Export prints the slides in Chromium. Set it up once in the project:
|
|
70
|
-
|
|
71
|
-
```sh
|
|
72
|
-
pnpm add -D @lincyaw/addon-publish playwright-chromium
|
|
73
|
-
pnpm exec playwright install chromium
|
|
74
|
-
```
|
|
75
|
-
|
|
76
|
-
and list `'@lincyaw/addon-publish'` in the document metadata's `plugins`. Then, in the document folder:
|
|
77
|
-
|
|
78
|
-
```sh
|
|
79
|
-
pnpm exec presmium-export --format pdf --output lecture.pdf
|
|
80
|
-
```
|
|
81
|
-
|
|
82
|
-
| Option | Does |
|
|
83
|
-
|---|---|
|
|
84
|
-
| `--format pdf` (default), `png`, `pptx` | PDF; PNG images, one per slide, into the `--output` folder; PowerPoint, each slide a picture, the narration as speaker notes, no links |
|
|
85
|
-
| `--output <file or folder>` | Where to write |
|
|
86
|
-
| `--with-clicks` | One page (or image) per step instead of per slide |
|
|
87
|
-
| `--range 1,3-5` | Only these slides |
|
|
88
|
-
| `--dark` | The dark theme |
|
|
89
|
-
| `--timeout <ms>` | How long a page may take to be ready (default 120000) |
|
|
90
|
-
| `--json` | Print the result as JSON |
|
|
91
|
-
|
|
92
|
-
`presmium-export` builds its own copy of the slides before printing, so the site's `base` does not affect it. A PDF export checks that every link the slides show is still a link in the PDF, and exits with code 1 when one was lost. Exit code 2 means a page was missing or the export timed out: read the error, then retry or raise `--timeout`. A file from a failed run is not a finished export.
|
|
93
|
-
|
|
94
|
-
In the studio, **Export** in the command bar makes the same PDFs, images and PowerPoint (and lecture videos) without the publish plugin listed; the files can be opened, played and downloaded there.
|
|
95
|
-
|
|
96
|
-
Afterwards, open the file and check the page count, missing pages, long code running off the page and the key links. Code that readers can run in the browser is printed with its recorded output.
|
|
97
|
-
|
|
98
|
-
## Give students a runnable notebook
|
|
99
|
-
|
|
100
|
-
```sh
|
|
101
|
-
presmium build --to notebook
|
|
102
|
-
```
|
|
103
|
-
|
|
104
|
-
This writes `dist/notebook/<name>.ipynb`, named after the entry file (`lecture.ipynb` for `lecture.json`), with images and other files in `media/` beside it; hand out the whole `dist/notebook/` folder. The kernel is `python3` unless the `metadata.renderers.notebook` says otherwise. Interactive components that a notebook cannot hold become a static form; the build report lists them. To link them to the online version, set the web address:
|
|
105
|
-
|
|
106
|
-
```json
|
|
107
|
-
{ "notebook": { "kernel": "python3", "webUrl": "https://example.com/course/" } }
|
|
108
|
-
```
|
|
109
|
-
|
|
110
|
-
Open the notebook in Jupyter and check that images show and code cells run.
|
|
111
|
-
|
|
112
|
-
## Prepare an offline class
|
|
113
|
-
|
|
114
|
-
A built web site keeps each document's pages and search in a separate browser cache after that document is opened. The code runtimes (what runs code in the browser) are larger and fetched only the first time code runs. So, while still online:
|
|
115
|
-
|
|
116
|
-
1. Open every document you will teach from at its exact deployed address, in the browser you will teach with, and wait until each page has loaded.
|
|
117
|
-
2. Run each piece of code the class uses once, or, with the publish plugin listed, click **Save for offline use** in the toolbar, which fetches the runtimes in advance. The publish plugin also copies remote images into the document at build time, so they show offline.
|
|
118
|
-
3. Disconnect the network and rehearse in the same browser at the same address: moving through slides, search, media, running code.
|
|
119
|
-
|
|
120
|
-
Remote Jupyter, the classroom server and AI models still need the network. When the class must be fully offline, prepare recorded outputs or a runtime that works locally.
|
|
121
|
-
|
|
122
|
-
`metadata.presmium["presmium.publish"].offline = false` in the document metadata turns the offline cache off; check whether it is set. Rehearse again after the site's address changes or after a rebuild: "it was opened before" does not prove this build's files are all cached.
|
|
@@ -1,74 +0,0 @@
|
|
|
1
|
-
# Narration, speech and lecture production
|
|
2
|
-
|
|
3
|
-
`lecture.json` is the only content authority. Narrations contain typed text, pronunciation and cue nodes; steps name narration IDs. Read the installed kernel contract for exact fields. Captions, spoken text and alignments derive from the same narration structure. A transcript becomes authored text only through an explicit adopt action. Read a Whisper transcript before adopting it: `.en` models translate non-English speech into English; it invents "Thank you." over silence, so drop words that start inside a final silence (`silencedetect=noise=-35dB:d=0.6`); more than 20% `♪` or `�` tokens means it failed; Chinese can come back as one "word" per sentence, sometimes in Traditional characters for Simplified speech, so split it into phrases and spread the time by character count.
|
|
4
|
-
|
|
5
|
-
## Open the saved version in the studio
|
|
6
|
-
|
|
7
|
-
Use the document toolbar's presentation preview action after the authoring save is acknowledged. Preparation compiles the exact confirmed document and stays in the editor until compilation succeeds. Continue editing to cancel that transition; a late response must not take the author away from new input or another document. A compilation error leaves the document and draft intact with a readable failure.
|
|
8
|
-
|
|
9
|
-
The presentation identifies its confirmed source version. When the source or an observed project dependency changes, use the refresh icon's explicit recompile action to adopt the new result. Unconfirmed runtime revisions are hidden. This version check does not freeze historical project assets or external dependencies.
|
|
10
|
-
|
|
11
|
-
To embed a lecture in another page of the same site, put its presentation in an iframe: `slides/?view=present&track=<id>&autoplay`, adding `§ion=<id>&step=<k>` to start at a step. The player starts once it is ready; browsers allow sound only after a click on the embedding page, so load the iframe from that click. Where the browser still refuses, the presentation waits at its start with a large Play button. The presentation posts `{ type: 'presmium:state', drawn, section, step, lecture }` to the embedding page (`lecture`: `loading`, `waiting`, `playing`, `paused` or `failed`); `whenPresentationReady` from `@lincyaw/presmium/site` waits for it. Audio clips are positioned by seeking, so the host must answer byte-range requests (GitHub Pages does).
|
|
12
|
-
|
|
13
|
-
Keys while presenting: left/right arrows move a step, Space plays or pauses the lecture (with nothing to play it moves to the next step), O opens the overview, Shift+F goes full screen, Escape ends the show. In Video production, Space plays or pauses and left/right arrows select the previous or next step across pages, also while the preview has the focus. Ctrl+S (⌘S) saves at once anywhere in the studio. Text fields, editors, open menus and dialogs keep their keys; a control reached with Tab keeps Space; after a click on a control, Space and the arrows do the shortcut instead of pressing that control again. Settings → Keyboard Shortcuts lists these keys.
|
|
14
|
-
|
|
15
|
-
## Edit scripts and voices in video production
|
|
16
|
-
|
|
17
|
-
Use the document toolbar's **Video production** action for the independent production workspace. Its page and step controls select stable authoring steps; the script and timing fields write to the same canonical source. The visual preview compiles a confirmed saved version separately. Returning to the document retains the original body editor.
|
|
18
|
-
|
|
19
|
-
In Document editor, **Captions** opens only caption text and narration start. Pronunciation tools, hold, trailing pause and media properties belong in Video production; do not add routine explanations of the data model to the editor.
|
|
20
|
-
|
|
21
|
-
**Choose a voice** edits a recoverable settings draft. Choose this step, selected steps, this page or the document; review the affected scope before applying. Batch changes preserve independent settings by default, including explicit silence and recording sources. Replacing them requires a separate count-based confirmation. Restoring inheritance removes voice settings at the chosen level; it does not mean explicit silence. A changed source invalidates the confirmation and keeps the draft.
|
|
22
|
-
|
|
23
|
-
**Clone a voice…** appears under the voice list when the speech service can train cloned voices. It trains a voice from one person's recordings: give the voice a name (on Volcengine, a voice slot bought in its console, starting with `S_`, or a new name for a pay-as-you-go voice), the speaker and where the voice may be used; then record or choose two recordings of that speaker, the consent statement the dialog shows read aloud, and a 10 to 30 second sample. Recordings are converted to 24 kHz mono WAV in the browser. Training asks for its own confirmation because the provider charges for it; the consent record is saved on this machine before the sample is sent. The dialog then follows the training until it is ready and **Use this voice** selects it in the voice draft. Cloned voices are off until the operator allows them in the workspace settings, and without the consent record the voice cannot be synthesized. A pay-as-you-go Volcengine voice is charged at its first synthesis, previews included, and cannot be retrained after that: audition it deliberately.
|
|
24
|
-
|
|
25
|
-
Auditions and batch generation retain their confirmation. In Video production, clicking Play authorizes one cancellable on-demand playback: exact cached audio plays immediately; missing speech buffers, uses the shared voiceover job and cache, then continues in the same mounted player. Pause, step navigation, another audio start, or source/project changes retire that intent. Explicit silence and recordings never become TTS. No connected provider does not invalidate exact existing cache audio. The generation dialog reports actual cache, missing and unavailable counts; these are not a price quote. Closing requests cancellation of work confirmed in that dialog, retaining completed exact caches. Video production provides local audio import and clip forms as described below. Video files and subtitle alignment are not yet supported. In Video production, **Original audio** records a candidate or selects saved audio. **Save as audio asset** only saves the material; **Use as step voiceover** explicitly adopts the whole file for this stable step through the same authoring API as MCP.
|
|
26
|
-
|
|
27
|
-
The production timeline shows the current page's visuals, voiceover and captions from the shared `ProductionPlan`. Waveforms come from decoding the actual cached audio. The exact position field uses seconds relative to the page; the transport displays time in the whole lecture. Seeking pauses first and uses the existing lecture player to reconstruct the selected step. Zoom and fit change only the view. On narrow screens use Pages and Assets, Visuals, Step Properties, and Timeline; the inspector has Script, Voiceover, and Captions tabs. Changing tabs retains the same playback runtime.
|
|
28
|
-
|
|
29
|
-
Focus an overflowing caption to read its complete text with native wheel, Home/End, PageUp/PageDown, up/down arrows or Space; Shift+Space scrolls up. These reading keys do not select another step. Left/right arrows and Escape retain the existing presentation behavior. Captions are not automatically split or realigned by scrolling.
|
|
30
|
-
|
|
31
|
-
With genuine word timing and a complete display-text mapping, Web playback and VTT use readable caption groups from the same production plan. In Video, fine-pointer users can activate a confirmed caption group to pause and seek its actual word boundary. With a coarse pointer, choose the stable step using the existing full-size buttons, then use Caption segment: its 44px action selector works at default zoom and can select the same sentence again to return to its start. Native keyboard activation remains available; zoom changes only the view. Unaligned recording/silence, proportional timing, translations without their own timing and unreliable word mappings retain the whole caption. Grouping does not edit narration, resynthesize audio, create manual alignment or turn estimated timing into exact timing.
|
|
32
|
-
|
|
33
|
-
For an explicit manual arrangement, open **Set caption times** in Video after preparing the current step with actual audio. **Split at line breaks** partitions the original typed narration; enter each segment's start and end in seconds relative to the step, then Apply. Times must increase without overlap and stay within that step. The original text, audio, pronunciation and cues stay unchanged; this is manual segment timing, never word alignment. Web, VTT and burned captions share the same segments and leave authored gaps blank. Changing narration, audio or step timing invalidates the old map until explicit review; replacing audio does not silently rebind its times. Restore automatic removes the manual map through the same action boundary. This form retains pending input across closing and step changes only while the same Video session remains mounted; leaving Video or reloading has no draft recovery. Doc keeps caption text and narration start only.
|
|
34
|
-
|
|
35
|
-
Only confirmed timing permits arbitrary time seeking and export. Video production can play stable steps with estimated missing speech, buffering at each missing utterance instead of silently advancing; unknown animation duration, unsupported recording cues/video clips and silent text-anchored cues have explicit diagnostics. Step selection remains available. Explicit `none` supports simple silent scripts and authored hold/pause timing without a provider; an unset voice with narration is not silence. A nonzero text cue in a silent script needs confirmed timing or audio.
|
|
36
|
-
|
|
37
|
-
Documents created in Studio declare the standard production plugins and lecture renderer. Studio's new documents and pages hold each static step for 4 seconds plus a 0.5-second trailing pause; validation does not insert these defaults into other documents. Existing documents keep their source unchanged until the author chooses Enable video production; enabling does not select a voice or generate speech. Use the production toolbar's compile icon after source changes or an explicit cache update. An unchanged plan remains paused at its actual time and rate; a new source or plan invalidates the old playback binding.
|
|
38
|
-
|
|
39
|
-
## Configure the intended source
|
|
40
|
-
|
|
41
|
-
Put lecture renderer options in `metadata.renderers.lecture`. Put timing and voice choice only in `production`: document defaults, optional section overrides and step overrides. A voice source is `none`, TTS with an actual engine/voice, or a recording asset. Do not keep a second `voice` or timing decision on renderer options, a step or narration text.
|
|
42
|
-
|
|
43
|
-
In Studio, use Settings → Voice Service (also linked from Video Production → Voiceover). The page defaults to Volcengine speech synthesis 2.0 and accepts a speech-console API Key, or an access token with its matching optional App ID. No Secret Key or console-version choice is needed. Empty inputs keep saved credentials; a new key without an App ID switches to API-key authentication. Save applies immediately; it does not select a voice or generate audio. Credentials stay in the local operator directory outside the workspace and are never returned by reads. Check Configuration only checks the saved local configuration; real provider permissions are checked by explicit playback, a confirmed sample, or batch generation after the service is enabled. Clearing the saved key restores any launch-environment fallback.
|
|
44
|
-
|
|
45
|
-
TTS providers, credentials and endpoints are operator configuration. Check the speech service's real engines and voice catalogue. `unavailable` differs from an empty available list. Unknown parameter capability stays unknown; do not imply unsupported style/rate options work.
|
|
46
|
-
|
|
47
|
-
## Generate explicitly
|
|
48
|
-
|
|
49
|
-
A cache-only preview can play existing exact-text/exact-voice audio; missing audio is generated on the explicit Video Play intent, or through batch generation before export. Use the installed lecture/speech generation action or documented API to synthesize an explicit revision-bound scope. Show provider, count and target before a paid operation. Never synthesize merely by opening the document, editing text, auditioning another voice or refreshing preview.
|
|
50
|
-
|
|
51
|
-
Checks, lecture builds and video exports read only exact cached voiceover. A configured engine does not make missing audio ready: generate it explicitly before exporting; these read/output actions never synthesize it.
|
|
52
|
-
|
|
53
|
-
The video export encodes with FFmpeg when it is installed (`ffmpeg` on the path, or `PRESMIUM_FFMPEG` naming the program) and then writes MP4 (H.264, AAC) at full quality. Without it the export falls back to a WebM encoded in the browser, which is softer, and its warning gives the install command. Before exporting a video for others, make sure FFmpeg is installed: `brew install ffmpeg` (macOS), `sudo apt install ffmpeg` (Debian, Ubuntu), `winget install --id Gyan.FFmpeg` (Windows).
|
|
54
|
-
|
|
55
|
-
Completed audio belongs to the exact content and voice configuration that produced it. Old callbacks cannot clear new input or label old audio current. Cancellation stops remaining work and retains completed valid cache. Reuse requires the synthesis key, current non-credential engine profile and actual audio SHA. Without that engine configured, commit the cache and matching speech lock: one locked profile can satisfy a request; multiple profiles are ambiguous. Builds and exports preserve the document's speech lock, including clips omitted by audience or form filtering. Legacy locked audio is still readable offline, but is not proof of a configured provider's identity. Unknown or mismatched alignment bindings are unavailable, not precise timing.
|
|
56
|
-
|
|
57
|
-
## Align and produce
|
|
58
|
-
|
|
59
|
-
Cue content supplies stable targets and actions; `production.cueTimings` owns delays. Timing defaults/overrides decide narration start, minimum hold and trailing pause. Recording/media clips use asset references, explicit source ranges and step attachments. Derived absolute playback times stay in the playback plan.
|
|
60
|
-
|
|
61
|
-
Local audio `production.mediaClips` can reference an existing canonical audio asset in the same document. Set `sourceRange` in milliseconds, an attached stable step and offset, `volume` from 0 to 1, and optional `muted`; muting retains the volume. The inspected audio range must fit entirely inside that confirmed step. Adjust trimming, offset or the authored hold when it does not fit; the plan does not retime cues or cross steps automatically. These clips mix with cached speech in preview and video export, without generating or changing captions. Files must be non-hidden, regular local audio; symlinks, remote/shared paths and video are rejected. Use the source-bound `production-asset` reader to inspect a referenced AssetID and the plan diagnostics to confirm availability. Saving JSON does not confirm the actual audio range.
|
|
62
|
-
|
|
63
|
-
To use original audio as narration, use Video’s **Original audio → Use as step voiceover**, or explicitly call the shared `adopt_recording` action for a saved source, stable step, audio asset and actual SHA-256; see `DocumentRecordingAdoption`. This sets `voiceSource.recording`, never a fabricated media clip. Each effective step plays its selected source range once; without a range it plays the whole file. In Video, **Narration range** edits the already adopted same-asset step with real in/out bounds. Restore full changes pending input and needs explicit Apply. Editing one step does not trim the asset or another step. Without an explicitly applied valid manual timing map, current Narration display text forms one whole-clip caption without word alignment; empty narration produces no caption. Trim keeps the whole authored script as an unaligned step caption and requires review; original ASR word times do not become trimmed alignment. Continuous cross-step recording, internal pauses, non-start cues and conflicting narration starts remain unsupported. Adoption preserves all narration and pronunciation, and does not start ASR, TTS or playback. The accepted version is prepared paused; late replies preserve newer input and microphone captures. Browser-controlled recording evidence does not verify a physical microphone, and MCP recording-client control is not connected.
|
|
64
|
-
|
|
65
|
-
In Video production, use **Audio clip → Import audio**, then select the asset and edit the paired in/out fields, step offset, volume and mute. Import only adds an asset; **Add to step** or **Apply** explicitly saves the clip. Invalid text remains editable. **Restore full** changes the pending range; removing a clip retains the asset. Pending input follows its document, stable step and clip; accepting a saved media change prepares that version and stays paused.
|
|
66
|
-
|
|
67
|
-
The workspace authoring API imports original audio through `document/audio`: multipart fields are `change` (JSON with `id` and `baseDocumentVersion`) and `file`. Original bytes and the canonical asset declaration share one version-checked transaction and history entry. The same route's GET uses `assetId` and `baseDocumentVersion` to inspect even an unused declared asset, without requesting compilation. Explicit `document/media-clip` changes carry the source version and full production binding; they save trim, offset, gain and mute only when the real range fits a confirmed step.
|
|
68
|
-
|
|
69
|
-
```sh
|
|
70
|
-
presmium check lesson --json
|
|
71
|
-
presmium build lesson --to lecture
|
|
72
|
-
```
|
|
73
|
-
|
|
74
|
-
Build only when the required speech cache and provider capability actually exist. Inspect missing/stale diagnostics, caption text, pronunciation, cue timing, arbitrary step navigation and the exported video. A prior successful snapshot must be visibly identified when current compilation failed.
|