Skip to content

Commit e30afa5

Browse files
authored
Merge pull request #83 from missing-elements/docs/guide-archive-setup
docs(guide): the build archive named in step 1, and under its own heading in step 4
2 parents e5038bd + f0e384b commit e30afa5

1 file changed

Lines changed: 22 additions & 8 deletions

File tree

‎src/h5p/create-with-ai/index.njk‎

Lines changed: 22 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,18 @@ csp: "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; o
111111
nothing that runs, which you can read
112112
<a href="https://github.com/missing-elements/h5p-toolkit/tree/main/skills/h5p-author">on GitHub</a>.
113113
</p>
114+
{#- The archive is named here too (the owner, 2026-11-20): a reader sets a chat up in this
115+
step, and one who never reached the end of step 4 did not learn there is an archive.
116+
For a chat with projects it is set up once, as the skill is. Step 4 keeps the whole of
117+
it, with what to do in a chat that has no projects. -#}
118+
<p>
119+
<strong>If your chat has projects</strong>, give it one more file, once: add
120+
<a href="/h5p/bundles/h5p-author-build.tar.gz" download>h5p-author-build.tar.gz</a>, the
121+
build archive, to a project, and ask in a chat of that project. The archive holds the
122+
build tool, so a chat whose code runs Node.js makes the <code>.h5p</code> file itself,
123+
even where it cannot download the tool. With no projects, you attach the archive to a
124+
message when the chat needs it, as <a href="#archive">step 4</a> says.
125+
</p>
114126
</section>
115127

116128
<section class="step" aria-labelledby="ask-heading">
@@ -156,14 +168,16 @@ csp: "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; o
156168
with Download the .h5p. A chat that built the file gives its source file too: open it on the
157169
build page to play the activity before you use it.
158170
</p>
159-
{#- The archive is offered here, where a reader has just seen which of the two their chat
160-
gave, and not in step 1: nobody can tell beforehand whether a chat's code downloads the
161-
tool, and the skill's own reply offers the archive where it would help (route 4's fixed
162-
line). A project is any chat's, not one product's: a chat that has projects keeps their
163-
files for every chat in them, and the skill looks for the archive among the chat's files
164-
wherever it came from (route 1). Where a project does not hand its files to the chat's
165-
code, the reader attaches it, which the step says too. -#}
166-
<p id="archive">
171+
{#- The whole of the archive is here, under a heading of its own, where a reader has just
172+
seen which of the two their chat gave: nobody can tell beforehand whether a chat's code
173+
downloads the tool, and the skill's own reply offers the archive where it would help
174+
(route 4's fixed line). Step 1 names it too, for a chat with projects. A project is any
175+
chat's, not one product's: a chat that has projects keeps their files for every chat in
176+
them, and the skill looks for the archive among the chat's files wherever it came from
177+
(route 1). Where a project does not hand its files to the chat's code, the reader
178+
attaches it, which the step says too. The heading keeps the id the build page links to. -#}
179+
<h3 id="archive">The build archive, for a chat that cannot download the tool</h3>
180+
<p>
167181
A chat that runs code and still hands over the source could not download the build tool,
168182
and its reply says so. Give it the tool yourself: download
169183
<a href="/h5p/bundles/h5p-author-build.tar.gz" download>h5p-author-build.tar.gz</a>, the

0 commit comments

Comments
 (0)