feat(admin): editable gallery Portable Text block (no TipTap editor node — import/render-only)

[khoinguyenpham04]

This Roadmap discussion mirrors #1436: feat(admin): editable gallery Portable Text block (no TipTap editor node — import/render-only).

Use this discussion to upvote the roadmap item and discuss priority, use cases, and product feedback. Keep implementation tracking, reproduction details, and PR-specific feedback on the source issue.

• Source issue: #1436
• Status: Open
• Labels: None
• Original author: SailingGreg

Original Issue

Summary

EmDash has a gallery Portable Text block, but it's import/render-only — there's no TipTap editor node, so a migrated gallery can't be inserted, edited, or reordered in the admin.

Current state

• Import: @​emdash-cms/gutenberg-to-portable-text defines PortableTextGalleryBlock (_type: "gallery", images[], columns?).
• Render: packages/core/src/components/Gallery.astro renders it and is registered by default in the PortableText component (components/index.ts).
• Edit: ❌ nothing in packages/admin/src/components/editor/ handles gallery (unlike image → ImageNode.tsx / ImageDetailPanel.tsx). A gallery that arrives via import is invisible/uneditable in the editor.

Request

A TipTap node + sidebar UI for the gallery block, mirroring the image handling:

• insert a gallery, add/remove/reorder images (media picker)
• set columns
• node-view preview in the editor

Why

WordPress migrations (WP Media Folder / Gutenberg galleries) bring gallery blocks through cleanly, but authors then can't manage them post-import — they have to drop to the seed/JSON. Closing the loop (like the recent image-alignment editor work) would make galleries first-class.

Notes

Related but distinct: #1369 / #1424 concern repeater/array field types with media. This is specifically the Portable Text gallery block in the rich-text editor.