The collection id lives in the URL, so it outlives the row. Delete one with it open — or have somebody
else delete it — and the address still asks for it, which made the media fetch 404 and put "Not found"
across a panel that was otherwise working perfectly. An error about the URL, phrased as an error about
the server.
Now a selection naming nothing is quietly removed from the URL. There is nothing anybody could do
about it and the correct state is simply "nothing selected".
The error is also cleared when the selection moves. It was only cleared on the next failure, so a
message from the last collection stayed up over the new one and read as this one having failed too.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The version before this made a collection out of every folder under originals/COLLECTIONS/. It kept
the disk and the database in step for free, and it also let whoever last tidied a directory decide the
website's structure. A collection is editorial: it exists because somebody made it, named it and put
photographs in it.
Its photographs are a GALLERY — the feature that already means "a named, ordered set of media", with a
picker and an order somebody dragged into place. A collection points at one rather than growing a
private copy, so ordering stays maintained in the one screen that owns ordering, and the same set can
appear in a collection and on a page without being chosen twice.
That is why the grid here is not draggable and has no Add: both belong to Galleries. What is decided
HERE is which photograph leads, because that is a fact about the collection rather than about the set.
Creating is a name and a button under the list it adds to, and it selects what it made — a dialog for
one field is a dialog nobody thanks you for. Deleting removes the collection and never the
photographs, which the button says out loud rather than leaving somebody to find out.
Changing the gallery clears the cover. The new set is different photographs, so a cover chosen from
the old one is a path that may not be there, and falling back silently would be a choice quietly
reverting itself.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Collections, above Galleries and Media, where the other things made of media already are.
There is no Create button and no Delete, and that is the design rather than an omission. Which
collections exist is a question about `originals/COLLECTIONS/`, so making one means making a folder —
in Media or in Finder, and both work. A Delete here would either drop the row and leave the
photographs, so the collection reappears on the next read, or delete somebody's pictures. Neither is
what Delete should mean in an admin.
The grid is for choosing the MAIN photo and nothing else. The photographs are already in filename
order and the gallery is the folder, so there is nothing to reorder and nothing to add — the one
decision is which picture leads. Pressing the chosen one again clears it, which is how "no choice, use
the first" stays reachable without a second control that only does that.
The badge says Main rather than Cover because it has to be true of the first photograph, which leads
by default, as well as of one somebody picked.
The fields are the other half — everything a directory cannot tell you: the name it goes by, the
address, and the specs from the client's sitemap. `folder` is shown and not editable, and the API
refuses to write it: it is an address, and renaming one moves files. Shown anyway, because it is the
only thing that says WHICH folder a collection is.
One draft, one save. Per-field writes would be eight requests for somebody filling in a form, and the
last to land would win in an order nobody controls.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
pastilhasandClaude Opus 5