a gallery is a carousel
It always rendered as one — data-carousel, a snap track, two arrows, driven by carousel.client.js. The entity was the last thing still calling it something else, and that collided with the site's own Gallery section: two nav rows reading Gallery and Galleries, meaning a list of objects and a list of photograph sets. GalleriesPanel, GalleryPicker and GalleryItems become Carousels*, the endpoint becomes /fofos-admin/carousels, the block kind becomes carousel and subject-gallery becomes subject-carousel. The publish allowlist follows the renamed tables. What did NOT move: GALLERY_CONFIG at /fofos-admin/gallery, subjects.ts's base '/gallery', and home_gallery_media. Those are the Gallery section and the legacy rows, and both are correct. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -19,7 +19,7 @@ import { thumbUrl } from '../thumbnail';
|
||||
* That is worth saying out loud in the panel, because the editor sits inside a block on a page and
|
||||
* everything else in that column belongs to the page.
|
||||
*
|
||||
* ── The same shape as GalleryItems ──
|
||||
* ── The same shape as CarouselItems ──
|
||||
*
|
||||
* Drag to reorder, a grip on the left, one write at the end carrying every id. Deliberately, so the
|
||||
* two ordered lists in this admin are the same gesture rather than two things to learn.
|
||||
@@ -64,7 +64,7 @@ export const PartnersEditor = ({ onChanged }: { onChanged?: () => void }) => {
|
||||
}
|
||||
};
|
||||
|
||||
/* Reordering, live. Same as GalleryItems — see the note there. */
|
||||
/* Reordering, live. Same as CarouselItems — see the note there. */
|
||||
const [dragged, setDragged] = useState<number | null>(null);
|
||||
const orderedRef = useRef<Partner[] | null>(null);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user