docs(guide): the build archive named in step 1, and under its own heading in step 4
Merged
AL
3d ago+22+22+01234567890123456789-8-8-0123456789
Closes #82.
What changes
On /h5p/create-with-ai/:
- Step 1 ends with a paragraph for a chat that has projects: add
h5p-author-build.tar.gzto a project, once, and ask in a chat of that project. It says what the archive is for (a chat whose code runs Node.js then makes the.h5pfile itself, even where it cannot download the tool), and that with no projects the archive is attached to a message, as step 4 says. - Step 4: the archive's part has a heading, "The build archive, for a chat that cannot download the tool". The
#archiveid moved from the paragraph to the heading, so the build page's link and step 4's own still land there.
The text of step 4 is otherwise unchanged. Both go by what a chat has (projects, code that runs Node.js), not by its name (#80).
Checked
pnpm run buildpasses.- In Chromium at 1280 and 390 px: no horizontal overflow, and
#archivelands on the new heading. Oneid="archive"in the page.
Summary by cubic
Documents the build archive in step 1 of the create-with-AI guide, so readers learn about it when setting up a chat, and gives step 4's archive instructions their own heading.
- Step 1 tells readers with projects to add
h5p-author-build.tar.gzto a project once, since chats whose code runs Node.js build the.h5pfile themselves without downloading the tool. - Step 4's archive instructions now sit under the heading "The build archive, for a chat that cannot download the tool", which keeps the
#archiveid so existing links still land there.