Yes. Modula Lite and Modula Pro both store galleries as the modula-gallery CPT with image data in postmeta. SleekView reads that the same way regardless of edition. Pro features such as Watermarking, Speed Up, Slideshow, Video support, and Roles surface as additional columns automatically when the relevant addons are active.

Yes. The image view exposes one row per image with file, alt text, title, caption, and link target, plus any addon-specific fields. Filter by gallery to scope down, or filter by missing-field booleans to surface accessibility gaps across the entire library at once for a focused remediation pass.

Yes. Albums use the modula-albums CPT and group galleries together. SleekView surfaces a per-album view with bundled gallery list, total image count, and album-level configuration. Useful for portfolio sites where albums are the navigation unit and the operator needs a quick overview of bundle composition.

Yes for title, grid type, lightbox toggle, and visibility. SleekView writes through Modula's own save path so any cache layer, gallery rebuild, or addon hook fires the same way it does from the plugin's UI. Image reordering edits best in the gallery edit screen because of the drag-and-drop UI.

Yes when the Modula Video addon is active. Video items in a gallery write their source provider and embed configuration to the same postmeta, and SleekView surfaces those as filterable columns. Mixed media galleries can be filtered by item type for a focused review.

Yes. SleekView uses Modula's standard save path, so the gallery rebuild, any object cache, and any page cache layer respond to the post update the same way they would from a save in the gallery edit screen. Front-end output stays consistent with the configuration in the table.

Yes. Each subsite stores galleries in its own wp_posts and wp_postmeta, with its own table prefix, and SleekView respects that scoping. Per-subsite admins see only their galleries; network admins can switch between sites and each one renders its own gallery list independently.

Yes. Any filtered view exports to CSV from the table header, with active filters and column order respected. Useful for accessibility audits, rights-management reports, or portfolio overviews shared with a client without giving them WP Admin access to the underlying gallery edit screens.