The portfolio is a separate content type, plus a page that shows everything
The vendor describes the portfolio as two pieces: work is published through "a latest post type", and there is "a custom page to display all your images". Treat those as different jobs. The post type holds one project, series or shoot per entry and gives it an addressable URL. The custom page is the browse-everything view that visitors land on first.
That split decides how you catalogue. One entry per series rather than one entry per photograph keeps the gallery readable and gives each body of work a page you can link from an exhibition listing or a press mention. It also keeps the archive page from filling up with near-identical thumbnails from the same shoot.
The vendor also lists an Ajax load-more behaviour for gallery listings. Visitors pull further items in without leaving the grid, which suits image-heavy archives where page numbers interrupt the browsing. It does mean a long archive loads in stages, so the behaviour is worth judging against your actual image count and file weights rather than a demo's smaller set.
Which builder you actually get is the first thing to settle
The marketplace compatibility field for Red Art names Elementor and Elementor Pro. The vendor description, written separately, is built around Visual Composer: it lists "Visual Composer Compatible" and "Customized Visual Composer shortcodes" and opens the feature list with a Visual Composer section about laying out gallery pages without code. The description's changelog is then split into two separate links, one labelled Elementor and one labelled WPBakery Page Builder.
So the product has been maintained along two tracks, and the listing's compatibility field captures only one of them. Before planning pages, check which builder the theme you install is configured for. The practical test is to import a sample or demo layout on a staging copy and see whether the prebuilt pages arrive as Elementor documents or as WPBakery ones. Layouts do not convert between the two, so a project started on the wrong track means rebuilding rather than porting.
The demo address recorded on the listing points to a Red Art page with "elementor" in the path, which fits the Elementor track for that preview. That is a naming observation about one URL, not a statement about what any package contains.
Blog layouts that can differ by category
The vendor names three blog layouts — Medium Blog, Medium 1 Col Blog and Single Blog — each available with or without a sidebar, and says the choice can change "on a page by page basis" as well as per category.
That granularity matters more than the count. An artist site usually runs at least two kinds of writing: short, frequent updates such as openings, press notes and works in progress, and long-form statements or essays. A multi-column arrangement suits the first; a single column without a sidebar lets the second run without a competing column. Setting the choice at category level means the distinction persists after you publish, instead of depending on each author remembering a page setting.
The vendor does not say whether individual posts can override the layout, so plan around the page and category levels, which are the documented ones.
Skins, light and dark, and the surrounding appearance controls
The feature list counts 20 skins with easy custom skin support, plus light and dark versions of the theme. For a gallery, that is not only branding: the surround changes how images read. Bright or high-contrast work gains from a dark canvas; paper-white, pastel or pale photography sits more calmly on a light one.
Because the light and dark variants change the canvas beneath every image on every page, decide between them early, while you are still judging a small set of images. The 20 skins cover common starting points, and the vendor's note that a custom skin is possible covers the case where an established identity colour has to carry through. A sticky menu, six menu styles and a style picker are also listed, but those are appearance decisions you can defer without affecting how the work is presented.
A slider manager handles responsive or full-width slides with captions and animation, which covers the usual opening screen for a portfolio rather than any specific gallery feature.
Exhibitions, ticket sales, and the smaller modules around them
The vendor's event calendar module covers forthcoming shows, tour dates and openings, and it states that you can sell tickets through it. That puts dates in a structured module instead of a blog post that ages badly once the exhibition closes.
The description presents the event calendar and the WooCommerce shop as separate features, so if ticket sales are central to your plans, confirm which commerce mechanism the events module actually uses before you commit. Around these sit three smaller modules the vendor names: a Mailchimp subscription box, Contact Form 7 form support, and custom Google Maps for a contact page built from an address or location. Each is a vendor claim about what the theme can host, and each needs its plugin or external service configured on your installation.
The shop half is aimed at selling prints, photographs or designs, with a specially designed WooCommerce page and multiple shop layout options. The marketplace lists WooCommerce compatibility from 5.x through 10.x.
The demo photographs are licensed separately, and that shapes the first build
The vendor closes the description with a note that the images used in the demo are not included, that they are copyrighted, and that links to purchase the appropriate licences can be provided.
For an image-led theme this is the detail most likely to change a budget, because the demo's effect comes almost entirely from the work in it. Load your own photographs and the site will look different immediately — intended, but it also means the preview is not something you can publish as-is. Plan on licensing stock or shooting your own, and start your build with a small set of your own images so you can judge whether the gallery listings, the light or dark canvas and the load-more archive hold together without the demo's art direction.
The declared WordPress range runs from 5.6.x to 7.0.x, observed in the marketplace listing in November 2026. Those are declarations stored with the listing, not results from running the theme against your PHP version, plugin set or host, so newer stacks are worth a staging check first. WPML appears in the compatibility field as a plugin you supply and configure; the files list records PHP, CSS and JavaScript theme code.
Questions & answers
Should I build Red Art pages in Elementor or WPBakery?
The evidence points in two directions, so check your own install rather than choosing from the article. The marketplace compatibility field names Elementor and Elementor Pro; the vendor's feature list and changelog are written around Visual Composer and WPBakery, with two separate changelog links. Import a sample layout on staging and see which builder the pages arrive in, then build on that one.
Does the portfolio hold one entry per photo or one per project?
The vendor only says the portfolio uses its own post type plus a custom page that displays all your images. Nothing in the description fixes the granularity, so the choice is yours; one entry per series or shoot keeps the archive page readable and gives each body of work a linkable URL.
Are the demo's photographs included with the theme?
No. The vendor states that demo images are not included, that they are copyrighted, and that purchase links can be provided. You will need your own photography or licensed stock for a live site.
Can tickets for exhibitions be sold through the shop?
The vendor says the event calendar module can sell tickets, and separately describes a WooCommerce shop with multiple layouts. The description does not say the two use the same commerce mechanism, so confirm that in the demo if ticket sales are a requirement.
