Gallery Module
The gallery module is the central backbone that organises visual assets per module. Any gallery-capable module — content, service, product, page, news or video — can own its own gallery; images are organised per record and supervised from one dashboard.
- Module gallery bridge: a registry of gallery-capable modules using name, mod_name, mod_key and mod_value for durable binding.
- Automatic image processing: every upload produces an original copy (max 1920 px wide) and a thumbnail (max 500 px).
- Multiple images per gallery: unlimited image rows per gallery with name, upload date and record binding.
- Image renaming: managers holding the gallery role on the target module can rename display names.
- Bulk cleanup: removing a gallery module deletes every attached image row together with its files.
- Safe operations: moderation roles for records owned by others; ACL-based access control.
- One-step module enrolment: registering a new module in the gallery bridge takes a single call.
The Image Workflow
When a manager uploads an image to a record, the system produces two copies: the original resized to 1920 pixels wide and a thumbnail resized to 500 pixels. Files are stored under the module's static folder with a random key, eliminating collisions and accidental overwrites. Deleting a record removes both the database row and the physical files. Thumbnails power listing cards and carousels, while originals serve the full-size viewer.
Permissions and Module Registry
Every gallery operation is authorised against the gallery role on the target module; modifying galleries owned by another administrator requires the moderation role. A new module gains gallery support simply by being registered in the bridge. Galleries filter by module and record group, so missing visuals surface quickly and priorities stay clear.
Through the MCP/AI integration, galleries can be listed and images uploaded, renamed and deleted, letting AI agents manage the visual inventory without human intervention.