diff --git a/web/sections/CollectionFields.tsx b/web/sections/CollectionFields.tsx index b79e56c..8860b59 100644 --- a/web/sections/CollectionFields.tsx +++ b/web/sections/CollectionFields.tsx @@ -14,9 +14,9 @@ import type { Collection } from './collections'; * by reading it. This is the other half: the name it goes by, the address it lives at, and the specs * from the client's sitemap. None of it can be derived, so all of it is typed. * - * `folder` is shown and not editable. It is an address — renaming it moves files — and the API refuses - * to write it for the same reason. Showing it anyway matters: it is the only thing that says WHICH - * folder a collection is, and somebody looking at two similarly named ones needs to be able to tell. + * The gallery is not here. It is chosen beside the photographs it puts on screen, in the panel, where + * the consequence of choosing it is visible — a dropdown in a column of text fields would be the one + * control whose effect you cannot see. * * ── One draft, one save ── * @@ -103,12 +103,6 @@ export const CollectionFields = ({ ))} - {/* Read-only, and shown rather than hidden: it is the only thing that says which folder this is, - and the API refuses to write it because renaming one moves files on disk. */} -
{collection.folder ?? '—'}
-{error}
} + {selected && ( +Choose a collection.
+Choose a collection, or make one.
+ ) : !selected.gallery_id ? ( ++ No gallery yet. Choose one and its photographs appear here. +
) : photos === null ? (
-
- That folder is empty. Put photographs in {selected.folder}. -
+That gallery is empty. Add photographs to it in Galleries.
) : ( <>- {photos.length} photographs, in filename order. Click one to make it the main photo. + {photos.length} photographs, in the gallery’s order. Click one to make it the main photo.