Release of Version 1.2.0 #133

Merged
miko merged 66 commits from development into master 2026-11-05 21:38:31 +01:00
Owner

Guides get working copies with publishing and a version history, print, PDF and QR code labels, a step-by-step view, difficulty, duration, protective equipment, licenses and attachments, plus export, import and duplication of guides, Atom feeds, instance backups and a reworked guide editor.

added

  • Print: a guide prints without the titlebar, breadcrumb and buttons, with all of a step's images and their annotations, always light, and with an attribution line at the end: the instance, the guide's address, its owner and last edit, and kataba; "Print" next to the guide opens the print dialog (#90)
  • PDF download: "Download PDF" next to a guide, for everyone who may read it, gives an A4 PDF with the logo and instance name at the top of every page, page numbers, the description and all steps with their images and annotations, and the same attribution line at the end; its text is set in Inter, with Noto Sans CJK for Chinese, Japanese and Korean (#90)
  • Difficulty and estimated duration: a guide can have a difficulty (easy, medium, hard) and an estimated duration in hours and minutes, set in its properties; both are optional and show as badges in the guide's header, on its tile in the category grid, and in print and PDF (#92)
  • Protective equipment: a guide can call for any of eight kinds of personal protective equipment (eye, face, hearing and respiratory protection, safety gloves, safety shoes, protective clothing, tied-back hair and no jewellery), ticked in its properties; each shows as a pictogram in the style of an ISO 7010 mandatory sign with its name, prominently at the top of the guide and in print and PDF (#95)
  • Working copy and publishing: edits to a published guide go to its working copy, and readers keep seeing the latest published version until someone publishes again; the editor shows "Unpublished changes" with "Publish" (with an optional note) and "Discard changes", and the guide page gives editors a link to preview the working copy. Every publish keeps a version; published guides get their first version when the server starts (#106)
  • Version History: "Version History" in a guide's editor shows every published version, read-only and complete as readers saw it, with when, by whom and with which note it was published; a slider with a mark per version (and a last mark for the working copy's unpublished changes) moves between them. "Restore this version" replaces the working copy with the selected version, asking first if that loses unpublished changes; it publishes nothing (#107)
  • License: every guide has a license, chosen in its properties from Public Domain, CC0 1.0, the six Creative Commons 4.0 licenses and "All rights reserved"; it shows, linked to its text, in the guide's header and in the attribution line of print and PDF. New guides start with the default license, a new setting ("All rights reserved" at first); changing it leaves existing guides as they are, and existing guides got "All rights reserved". The license is part of a guide's versions (#103)
  • Atom feeds: /feed lists newly published and changed guides of the whole instance, /feed/<category path> those of a category and its subcategories, e.g. to post them into a Matrix or Discord channel. Each guide is one entry with its title, cover image, description, who published it and when; every new version updates it, with its change note in the summary, while saved changes to the working copy never show. Only guides guests may see appear, the 50 most recently published; pages link to the instance's feed and category pages to theirs for feed readers (#104)
  • Attachments: files can be attached to a guide for download, such as 3D models, drawings, G-code, manuals or firmware, several per guide, each with a name and an optional description; they are added (chosen or dropped), renamed and removed in the guide's properties and are part of its versions. The guide lists them with type and size below its description, and print and PDF name them with a hint where to download them. Attachments are always downloaded, never opened in the browser; programs and scripts (by extension, and every Windows program by its header) are refused. The largest attachment is a new setting, 50 MB at first (#97)
  • Export and import of guides: "Export" in a guide's editor downloads its working copy as a ZIP with all images and attachments, for everyone who may edit it; history, owner, visibility, wiki mode and menu entries stay behind. Admins import such a package under "Import guide" in the admin menu or on a category page, into a category of their choice, as a public draft of their own without wiki mode that keeps the package's license, protective equipment and attachments. Its content is checked like typed-in content, and packages from a newer kataba are refused (#108)
  • Step-by-Step View: "Step by step" in a guide's reading view opens it one step per screen, filling the window, for a tablet or phone at the machine: a start screen like a title slide, the title large and centred over the darkened cover image, with the number of steps, difficulty, duration, protective equipment, description and attachments; then each step using the whole window, its image as large as the height allows with its annotations, and its step lines and content beside it on wide screens, below it on narrow ones. Readers move by swiping, by the arrow keys or by large buttons, with "Step 4 of 12" and a progress bar at the top, and every screen has its own address (/guides/<id>/steps/<n>). The screen stays on, the view can switch to full screen, and steps can be checked off; that progress is kept only in the browser and starts over once a new version is published. A guide titled "Steps", whose address ended in /steps, now reads at /steps-2 (#98)
  • Labels with QR codes: "QR code" next to a guide's "Print" and "Download PDF", and on every category page, downloads a label as a PDF for everyone who may see the guide or category, to stick on a machine, cabinet or tool wall: a QR code with the title, the kataba mark and the instance name, laid out beside the code on a landscape label and below it otherwise. The code leads to an address by id, /guides/<id> or the new /categories/<id>, which redirects to the category page, so it keeps working after renaming or moving; internal content needs signing in, as before. The label size is a new setting, 50 × 30 mm at first, from 30 × 20 mm. A guide titled "Label", whose address ended in /label, now reads at /label-2, and a page can no longer take the slug "categories" (#94)
  • Instance backup: "Download backup" in the admin menu downloads the whole instance as a ZIP, streamed as it is written: users with their last known role, settings, categories with their images, guides with their working copies, all versions and deleted guides, pages with their images, the menu, and every image and attachment. It shares the guide packages' format version. npm run restore -- <backup.zip> restores it on the command line in the container, only into an empty instance, keeping the ids of guides, categories and pages so links and QR code labels keep working; backups from a newer kataba are refused (#109)
  • Duplicating guides: "Duplicate" in a guide's reading view and editor copies its working copy, for every author and admin who may see the guide, with all steps, step lines, images, annotations, cover image, effort, protective equipment, license and attachments; images and attachments get files of their own, so deleting the original leaves the copy whole. The copy is a draft of whoever duplicated it, titled "Copy of …", in the same category with the same visibility and without wiki mode; versions, menu entries and the status stay with the original (#100)

changed

  • Guide Actions Menu: in a guide's reading view, signed-in users find "QR code", "Duplicate", "Edit guide", "Unpublish" and "Delete guide" in a "…" menu next to "Print" and "Download PDF", so the row of buttons stays short; "Publish" stays a button. Guests keep "QR code" as a button (#124)
  • Saving in the guide editor: one "Save" button at the top of the sidebar (along the bottom edge on narrow screens) saves the open step, the title, language and description, and the properties together, in place of "Save step", "Save guide" and "Save properties"; Enter in a field saves too. Saving stays in the editor and says whether all changes are saved; a part that fails keeps its changes and error while the others are saved. Publishing from the editor saves first and leads to the reading view; discarding the unpublished changes shows the working copy afresh, so nothing discarded can be saved back. Leaving the editor with unsaved changes anywhere in it asks first (#125)
  • Guide editor sidebar: the properties are split into the tabs "General" (visibility, category, wiki mode, owner), "Details" (difficulty, estimated duration, protective equipment, license) and "Media" (cover image, attachments), with more whitespace between the fields; switching tabs keeps unsaved changes, a tab with unsaved changes is marked, the Save button saves all tabs together, and a failed save opens the tab with the unsaved changes (#126)
  • Media buttons in the guide editor: the buttons for the cover image (and a category's image) and for each attachment show only their icon, with their text in a small tooltip bubble on hover or keyboard focus; "Add files" keeps its text; wiki mode is a toggle switch instead of a checkbox (#130)

fixed

  • Dialogs (publish, discard, restore, crop, annotate) now darken the page behind them, and the crop frame's corner handle has its white border: the theme has no black or white, so both were silently missing; they use the new scrim colours
  • Dropdowns in forms, such as the settings' top-level child order, default language and default license, no longer jump back to the previous value after saving until the page is reloaded (#114)

🤖 Generated with Claude Code

Guides get working copies with publishing and a version history, print, PDF and QR code labels, a step-by-step view, difficulty, duration, protective equipment, licenses and attachments, plus export, import and duplication of guides, Atom feeds, instance backups and a reworked guide editor. ### added * Print: a guide prints without the titlebar, breadcrumb and buttons, with all of a step's images and their annotations, always light, and with an attribution line at the end: the instance, the guide's address, its owner and last edit, and kataba; "Print" next to the guide opens the print dialog (#90) * PDF download: "Download PDF" next to a guide, for everyone who may read it, gives an A4 PDF with the logo and instance name at the top of every page, page numbers, the description and all steps with their images and annotations, and the same attribution line at the end; its text is set in Inter, with Noto Sans CJK for Chinese, Japanese and Korean (#90) * Difficulty and estimated duration: a guide can have a difficulty (easy, medium, hard) and an estimated duration in hours and minutes, set in its properties; both are optional and show as badges in the guide's header, on its tile in the category grid, and in print and PDF (#92) * Protective equipment: a guide can call for any of eight kinds of personal protective equipment (eye, face, hearing and respiratory protection, safety gloves, safety shoes, protective clothing, tied-back hair and no jewellery), ticked in its properties; each shows as a pictogram in the style of an ISO 7010 mandatory sign with its name, prominently at the top of the guide and in print and PDF (#95) * Working copy and publishing: edits to a published guide go to its working copy, and readers keep seeing the latest published version until someone publishes again; the editor shows "Unpublished changes" with "Publish" (with an optional note) and "Discard changes", and the guide page gives editors a link to preview the working copy. Every publish keeps a version; published guides get their first version when the server starts (#106) * Version History: "Version History" in a guide's editor shows every published version, read-only and complete as readers saw it, with when, by whom and with which note it was published; a slider with a mark per version (and a last mark for the working copy's unpublished changes) moves between them. "Restore this version" replaces the working copy with the selected version, asking first if that loses unpublished changes; it publishes nothing (#107) * License: every guide has a license, chosen in its properties from Public Domain, CC0 1.0, the six Creative Commons 4.0 licenses and "All rights reserved"; it shows, linked to its text, in the guide's header and in the attribution line of print and PDF. New guides start with the default license, a new setting ("All rights reserved" at first); changing it leaves existing guides as they are, and existing guides got "All rights reserved". The license is part of a guide's versions (#103) * Atom feeds: `/feed` lists newly published and changed guides of the whole instance, `/feed/<category path>` those of a category and its subcategories, e.g. to post them into a Matrix or Discord channel. Each guide is one entry with its title, cover image, description, who published it and when; every new version updates it, with its change note in the summary, while saved changes to the working copy never show. Only guides guests may see appear, the 50 most recently published; pages link to the instance's feed and category pages to theirs for feed readers (#104) * Attachments: files can be attached to a guide for download, such as 3D models, drawings, G-code, manuals or firmware, several per guide, each with a name and an optional description; they are added (chosen or dropped), renamed and removed in the guide's properties and are part of its versions. The guide lists them with type and size below its description, and print and PDF name them with a hint where to download them. Attachments are always downloaded, never opened in the browser; programs and scripts (by extension, and every Windows program by its header) are refused. The largest attachment is a new setting, 50 MB at first (#97) * Export and import of guides: "Export" in a guide's editor downloads its working copy as a ZIP with all images and attachments, for everyone who may edit it; history, owner, visibility, wiki mode and menu entries stay behind. Admins import such a package under "Import guide" in the admin menu or on a category page, into a category of their choice, as a public draft of their own without wiki mode that keeps the package's license, protective equipment and attachments. Its content is checked like typed-in content, and packages from a newer kataba are refused (#108) * Step-by-Step View: "Step by step" in a guide's reading view opens it one step per screen, filling the window, for a tablet or phone at the machine: a start screen like a title slide, the title large and centred over the darkened cover image, with the number of steps, difficulty, duration, protective equipment, description and attachments; then each step using the whole window, its image as large as the height allows with its annotations, and its step lines and content beside it on wide screens, below it on narrow ones. Readers move by swiping, by the arrow keys or by large buttons, with "Step 4 of 12" and a progress bar at the top, and every screen has its own address (`/guides/<id>/steps/<n>`). The screen stays on, the view can switch to full screen, and steps can be checked off; that progress is kept only in the browser and starts over once a new version is published. A guide titled "Steps", whose address ended in `/steps`, now reads at `/steps-2` (#98) * Labels with QR codes: "QR code" next to a guide's "Print" and "Download PDF", and on every category page, downloads a label as a PDF for everyone who may see the guide or category, to stick on a machine, cabinet or tool wall: a QR code with the title, the kataba mark and the instance name, laid out beside the code on a landscape label and below it otherwise. The code leads to an address by id, `/guides/<id>` or the new `/categories/<id>`, which redirects to the category page, so it keeps working after renaming or moving; internal content needs signing in, as before. The label size is a new setting, 50 × 30 mm at first, from 30 × 20 mm. A guide titled "Label", whose address ended in `/label`, now reads at `/label-2`, and a page can no longer take the slug "categories" (#94) * Instance backup: "Download backup" in the admin menu downloads the whole instance as a ZIP, streamed as it is written: users with their last known role, settings, categories with their images, guides with their working copies, all versions and deleted guides, pages with their images, the menu, and every image and attachment. It shares the guide packages' format version. `npm run restore -- <backup.zip>` restores it on the command line in the container, only into an empty instance, keeping the ids of guides, categories and pages so links and QR code labels keep working; backups from a newer kataba are refused (#109) * Duplicating guides: "Duplicate" in a guide's reading view and editor copies its working copy, for every author and admin who may see the guide, with all steps, step lines, images, annotations, cover image, effort, protective equipment, license and attachments; images and attachments get files of their own, so deleting the original leaves the copy whole. The copy is a draft of whoever duplicated it, titled "Copy of …", in the same category with the same visibility and without wiki mode; versions, menu entries and the status stay with the original (#100) ### changed * Guide Actions Menu: in a guide's reading view, signed-in users find "QR code", "Duplicate", "Edit guide", "Unpublish" and "Delete guide" in a "…" menu next to "Print" and "Download PDF", so the row of buttons stays short; "Publish" stays a button. Guests keep "QR code" as a button (#124) * Saving in the guide editor: one "Save" button at the top of the sidebar (along the bottom edge on narrow screens) saves the open step, the title, language and description, and the properties together, in place of "Save step", "Save guide" and "Save properties"; Enter in a field saves too. Saving stays in the editor and says whether all changes are saved; a part that fails keeps its changes and error while the others are saved. Publishing from the editor saves first and leads to the reading view; discarding the unpublished changes shows the working copy afresh, so nothing discarded can be saved back. Leaving the editor with unsaved changes anywhere in it asks first (#125) * Guide editor sidebar: the properties are split into the tabs "General" (visibility, category, wiki mode, owner), "Details" (difficulty, estimated duration, protective equipment, license) and "Media" (cover image, attachments), with more whitespace between the fields; switching tabs keeps unsaved changes, a tab with unsaved changes is marked, the Save button saves all tabs together, and a failed save opens the tab with the unsaved changes (#126) * Media buttons in the guide editor: the buttons for the cover image (and a category's image) and for each attachment show only their icon, with their text in a small tooltip bubble on hover or keyboard focus; "Add files" keeps its text; wiki mode is a toggle switch instead of a checkbox (#130) ### fixed * Dialogs (publish, discard, restore, crop, annotate) now darken the page behind them, and the crop frame's corner handle has its white border: the theme has no black or white, so both were silently missing; they use the new scrim colours * Dropdowns in forms, such as the settings' top-level child order, default language and default license, no longer jump back to the previous value after saving until the page is reloaded (#114) 🤖 Generated with [Claude Code](https://claude.com/claude-code)
miko added 66 commits 2026-11-05 21:37:40 +01:00
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The guide page prints without the titlebar, breadcrumb and buttons, shows
every step image with its annotations on paper, always in the light theme,
and ends with an attribution line. "Download PDF" draws the guide with
react-pdf: logo header and page numbers on every page, the same
attribution line at the end (ADR-0019).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
react-pdf starts a dashed circle's dash elsewhere than browsers, which put
the ring's gap at the bottom left and ran it into the dot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Helvetica covered only Western European text. Inter, the interface's
font, now sets Latin, Greek and Cyrillic; Noto Sans CJK fills in Chinese,
Japanese and Korean glyph by glyph, code falls back to both. The fonts
(SIL OFL, licences beside them) are traced into the standalone build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #91
A guide can have an optional difficulty (easy, medium, hard) and an
estimated duration in minutes, entered as hours and minutes in its
properties. Both show as badges in the guide's header (and so in print),
on its tile in the category grid and in the PDF, e.g. "Medium" and
"about 1 h 30 min".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The difficulty is a button group like visibility, with "None" for no
difficulty; hours and minutes are input groups with "h" and "m" attached.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Footprints, mountain and snowy mountain for easy, medium and hard, a
dashed circle for none; each label on one line under its icon, all four
side by side, so the group fits the narrow properties column.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #110
A guide can call for any of eight kinds of personal protective equipment,
ticked in its properties. Each shows as a self-drawn pictogram in the style
of an ISO 7010 mandatory sign with its name, at the top of the guide and in
print and PDF.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ISO 7010 fixes a mandatory sign's colours, so they stay outside the theme.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #111
Edits to a published guide go to its working copy; readers keep seeing
the latest version until someone publishes again. Every publish stores
the content as a GuideVersion (JSON snapshot, publisher, optional note).
The reading view, print/PDF, category grids, menu, search and /media read
the latest version; editors get an "unpublished changes" badge with
Publish and Discard, and a preview of the working copy. Image files are
kept while a version references them. Published guides get their first
version at server start (ensureFirstVersions). ADR-0020 supersedes
ADR-0008; GLOSSARY gains Working Copy and Version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #112
The editor gains a Version History at /guides/<id>/edit/history: a native
range slider with a mark per version, and a distinct last mark for the
working copy when it has unpublished changes, selects one version at a
time (latest by default, ?version=N or working-copy). The selected version
renders read-only through the reading view's GuideArticle (embedded: h2
title, no breadcrumb or controls), with its time, publisher and note
above. "Restore this version" replaces the working copy with it and
publishes nothing, so the history stays linear; it is disabled for the
working copy and for a version the working copy equals, and asks first
when unpublished changes would be lost. Discard and restore share one
locked reset helper. Guests get a 404 from the proxy. GLOSSARY gains
Version History.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #113
Every guide has a license, chosen in its properties: Public Domain (Public
Domain Mark 1.0), CC0 1.0, the six Creative Commons 4.0 licenses, or all
rights reserved. It shows, linked to its text, in the guide's header and in
the attribution line of print and PDF. New guides start with the default
license, a new setting ("all rights reserved" at first); changing it leaves
existing guides alone, and the migration gave them all rights reserved.

The license is versioned content (ADR-0020): readers see the published
one, and discard and restore bring a version's license back. A version
published before licenses existed reads as all rights reserved, so it
shows no unpublished changes. The properties form now remounts when the
guide's version changes, so after a discard or restore it shows the
working copy's properties, not the discarded ones. GLOSSARY gains License.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/feed lists newly published and changed guides of the whole instance,
/feed/<category path> those of a category and its subcategories, e.g. to
post them into a Matrix or Discord channel. Each guide is one entry, made
from its latest version: title, cover image, description, who published it
and when, with the version's change note in the summary; its first
version's time is the entry's publishing date. Saved changes to a working
copy never show. Only guides a guest may see appear (public effective
visibility), the 50 most recently published; a category that is missing
or hidden from guests answers 404.

Every page links the instance's feed in its head for feed readers, a
public category page also its own. "feed" becomes an app route name and so
a reserved page slug. GLOSSARY gains Feed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #115
# Conflicts:
#	CHANGELOG.md
Reviewed-on: #116
Files can be attached to a guide for download (3D models, drawings,
G-code, manuals, firmware), each with a name and optional description.
They are part of the working copy and its versions; their files stay as
long as a working copy or a version references them. The reading view
lists them with type and size, print and PDF name them with a hint.

Downloads go through the guarded /media route, always as attachment with
nosniff; programs and scripts are refused by extension (trailing dots
included) and by the MZ header. Uploads go to a route handler, since the
largest attachment is a new setting (50 MB at first). ADR-0021.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #117
Guides can be exported as a guide package: a ZIP with guide.json
(formatVersion and the working copy's content as VersionContent) and every
image original and attachment under its storage key, streamed with fflate.
Everyone who may edit a guide exports it from the editor.

Admins import packages under "Import guide" in the admin menu or on a
category page, into a chosen category, as a public draft of their own
without wiki mode that keeps the package's license. The content is
sanitised like typed-in content and gets fresh ids and files; packages from
a newer kataba are refused. ADR-0022 records the format, which the instance
backup (#109) is to reuse.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #118
A reading mode for a tablet or phone at the machine: "Step by step" in the
reading view opens /guides/<id>/steps, a start screen with title, effort,
protective equipment, description and attachments, then one step per
screen at /guides/<id>/steps/<n>, filling the window. Readers move by
swiping, arrow keys or large buttons; the address follows without a
reload. The screen stays on (Wake Lock), the view can go full screen, and
steps can be checked off in localStorage, bound to the published version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Guests get a real 404 for a step the published version lacks: the proxy
  counts the latest version's steps (ADR-0017).
- A guide slugged "steps" before the route reserved it reads at /steps-2;
  guideHref maps reserved slugs, and the reading view compares through it.
- The screen follows the address (usePathname), so reopening the view
  after Next kept it hidden starts at the overview again.
- Swipes are ignored while zoomed in or on content that scrolls sideways,
  and on touchcancel.
- The wake lock is taken again when the system drops it.
- The progress bar tells screen readers how many steps are done.
- StepBody shared by the reading view and the Step-by-Step View; progress
  functions moved to progress.ts; one modifier-key check; keydown handler
  as an effect event.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The start screen reads like a title slide: centred in the window, the
title very large, the number of steps above it. Steps use the whole
window: the image as large as the height left allows (sized against the
view's size container), with the step lines and content beside it on wide
screens and below it on narrow ones.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The start screen shows the guide's cover image behind its title, under a
scrim that keeps white text at about 5.8:1 even on a white photo. The
protective equipment, description and attachments stay below, on the
plain background. New semantic tokens scrim and on-scrim (ADR-0010), as
the theme has no black or white.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The theme resets Tailwind's colours (ADR-0010), so backdrop:bg-black/60 on
the publish, discard, restore, crop and annotate dialogs and border-white
on the crop frame's handle produced nothing. They now use the semantic
scrim and on-scrim tokens.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #119
"QR code" next to a guide's Print / Download PDF and on every category
page downloads a label PDF (react-pdf, ADR-0019): QR code to the id-based
address, title, kataba mark and instance name; landscape labels put the
code beside the text, others above it. New /categories/<id> redirects to
the category page; the label size is a new setting (50 × 30 mm default,
from 30 × 20 mm).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Landscape labels cap the QR code at 55 % of the width, so a label barely
wider than high still shows its title. Named the renderer's constants,
added labelSize(settings), shared the guest check for category chains,
and aligned the German wording with its neighbours.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #120
Admins download the whole instance as a streamed ZIP under "Download
backup" in the admin menu: users, settings, categories, guides with
working copies, all versions and deleted ones, pages, the menu and every
stored file, in the guide package format with the shared format version.
`npm run restore -- <backup.zip>` restores it into an empty instance only,
keeping every id. Written with yazl for ZIP64, read with yauzl; the CLI is
bundled with rolldown into dist/restore.mjs for the production image.
ADR-0023, glossary entry Backup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Share the format version check and package file rule with guide
packages, reuse VARIANTS and jsonColumn, warn about files missing from
the storage, and correct the docs: annotations get new ids, ADR-0013
names the REPEATABLE READ exception, README lists the new scripts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #122
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lock the original while reading its working copy, share freshFileKeys
with the package import, clearer names.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #123
React resets a form after its Server Action, and a select resets to the
option that was its default when it mounted, not to a defaultValue changed
since. A shared Select, keyed by its default, mounts afresh when the saved
value changes; every defaultValue select in the forms uses it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #127
QR code, Duplicate, Edit guide, Unpublish and Delete guide move from the
guide's button row into a "…" dropdown for every signed-in user; guests
keep QR code as a button and Publish stays a button.

TitlebarDropdown becomes Dropdown, with a configurable trigger, closing
on form submit, and keeping its panel inside the window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #128
"Save step", "Save guide" and "Save properties" become one Save button at
the top of the editor's sidebar (along the bottom edge on narrow screens).
It saves the dirty parts in order, step, guide, properties: a declined
confirmation stops the rest, a failed part shows its own error while the
others are saved. Saving the guide or its properties no longer leads to the
reading view; only publishing does. Enter in a field saves too, a status
line tells whether all changes are saved, and leaving the editor with
unsaved changes anywhere in it asks first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Publishing from the editor saves its unsaved changes first and publishes
nothing if that fails. Discarding forgets them and, like any working copy
replaced elsewhere, mounts the editor's body afresh, so discarded text can
no longer be saved back. The editor tells that apart from its own saves by
the guide versions they produce, so the properties form no longer remounts
(and loses its changes and error) when the guide content is saved.

The forms save against the version they were loaded with or last saved,
not the one a refresh brings, so a conflict stays a conflict on the next
save instead of overwriting someone else's changes.

The three forms share useEditorPartForm; rich text edit counting moves to
src/richText, ImplicitSubmit to src/forms, and the editor speaks of
"unsaved" parts throughout.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #129
The cover image, attachments, properties and ownership forms stood as far
apart as the fields within them; they are now set gap-8 apart, with the
heading and owner line kept together.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Difficulty, estimated duration, protective equipment and license ran
together at gap-4; the properties form now sets its fields gap-6 apart,
still closer than the gap-8 between the parts of the sidebar.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The properties form fills General (visibility, category, wiki mode) and
Details (difficulty, duration, protective equipment, license); the owner
continues General outside it, since forms cannot nest, and Media holds
the cover image and attachments. Every tab stays mounted and is only
hidden, so unsaved changes survive switching and one Save saves them
all; a tab whose fields have unsaved changes is marked. The tab list
follows the ARIA tabs pattern with arrow keys, Home and End.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From the review: the owner block is a second tabpanel of General, which
its tab now controls as well, so assistive technology ties it to the tab.
A failed save opens a tab with unsaved changes, where the error likely
is. Panels share one layout class, and the props read clearer
(secondary, markEdited). New e2e tests cover the failed save from the
Media tab and the owner in General.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #131
The cover image and attachment buttons show only their icon, their text in
a small speech bubble on hover and keyboard focus; "Add files" keeps its
text. Wiki mode is a toggle switch that still posts like a checkbox.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #132
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
miko merged commit 15511e9e50 into master 2026-11-05 21:38:31 +01:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
MassiveDynamic/kataba!133
No description provided.