The portfolio index is the real design decision
ART's feature list spends more space on how work gets listed than on any demo page. The vendor describes one portfolio module with two shapes, Standard Grid and Masonry Grid, and four places to pull items from: single posts, portfolio posts, WooCommerce products, and the media library.
That choice matters more than it sounds. A photographer's index probably wants portfolio entries. A studio that also sells prints could feed a shop category into the same grid. And pulling from the media library means you can build a grid of images that never existed as posts.
The controls around the list are equally specific. The vendor documents 1 to 12 columns, item spacing, an optional filter for visitors, and pagination as either a load-more button or infinite scroll. Captions can appear under the thumbnail, on mouseover, or not at all, with their own font, colour, spacing and alignment settings. If you already know how many pieces you want visible at once and whether you want a filter row, you can answer most of ART's portfolio questions from the listing itself.
Masonry you arrange by hand
Most masonry grids are calculated: the browser fills columns and the theme decides where each item lands. ART describes a separate drag-and-drop masonry editor, so the Masonry Grid layout is something you compose rather than something the layout engine produces.
That is a meaningful trade-off for artwork. A portrait painting, a landscape photograph and a wide installation shot do not tile evenly, and auto-flow masonry often leaves an awkward gap or pushes your strongest piece down the page. Placing items yourself costs time on large sets, but it lets you govern which work sits high in the grid and where the visual weight lands.
Nothing in the supplied material shows how that editor behaves with a hundred items, so treat the hand-placed approach as the right fit for curated, limited indexes rather than for an archive that grows continuously.
Project pages you compose from parts
The vendor calls ART a case-study portfolio system, and the single project template is described as unlimited rather than fixed. You mix elements — gallery, single image, heading, paragraph, slider, social icons, video — in whatever order the work needs.
Several named arrangements are listed as starting points: a text column beside a gallery column with the gallery on either side, filled or boxed; a full-width layout; a layout built around a slider; an irregular layout; and a heading masked by an image. A gallery lightbox lets visitors open images without leaving the page.
A lightbox also navigates across images from different modules according to the feature list, which is the detail that makes a case study feel like one continuous body of work rather than separate blocks. If your projects need a written narrative next to the images, the text-and-gallery column variants are the fastest route; if the images carry the page alone, the full-width layout is.
How ART is edited, and where the demos come from
ART bundles BM Content Builder, a front-end drag-and-drop editor the vendor describes as running in the browser with a what-you-see-is-what-you-get view. The vendor also states plainly that the demo data is built with BM Content Builder, and that demos install as pre-made templates through a one-click import.
That last point is worth holding onto. ART additionally supports page creation with Elementor and WPBakery Page Builder, but importing a demo gives you BM-built layouts, not Elementor or WPBakery documents. If your team standardises on one of those builders, you would be rebuilding imported pages rather than editing them.
If you prefer the block editor, the marketplace attributes mark ART as Gutenberg optimized, and the vendor lists it as Gutenberg editor ready — useful for simpler pages, though the portfolio and project layouts described above come from the BM modules.
Nineteen header layouts, and a separate mobile header
Headers are where ART's configuration depth becomes visible on every page. The vendor counts 19 layouts, naming top, side, overlay and logo-right among them, plus 3 dedicated mobile header layouts rather than a single collapsed version of the desktop bar.
Repeated header decisions run alongside those layouts: floating or fixed behaviour, custom height, custom colour, and either an image logo or a plain-text one. A dual logo option lets you serve a dark mark on light pages and a light mark on dark pages, and there is a separate logo setting for mobile.
A side or overlay header suits an image-led portfolio because it frees the top of the page for work. If your site mixes light and dark pages, the dual logo is the feature worth setting up before you start building pages, since retrofitting it means re-checking every page background.
Fonts, breakpoints and the mobile-sized details
The vendor's font library covers 900+ Google fonts, 1700+ Adobe fonts and fonts you upload yourself. More useful than the count is the control structure: font size, line height and letter spacing are set per element, and the theme allows a different font size for mobile.
The mobile section extends that thinking. Element spacing can be adjusted for small screens, icon and font sizes change, and the theme supports VW units for font sizing — so type scales with the viewport rather than snapping at a breakpoint. The vendor states that the web fonts used by the demo site are included in the package.
For a portfolio, this is the difference between a grid that stays legible on a phone and one that simply shrinks. It does mean more settings to manage; the sensible approach is to set desktop type first, then adjust the mobile-specific values rather than leaving them at defaults.
Declared compatibility and what the listing includes
The marketplace attributes record WordPress 6.0.x through 7.0.x, WooCommerce 7.x.x through 10.x.x, and WPML, observed on 4 November 2026. These are vendor declarations made at the time of the item update, not results on your own server. The vendor changelog shows ongoing WooCommerce compatibility updates, which is a better signal for a shop build than the version range alone.
WooCommerce product pages get their own named layouts: Vertical Slider, Minimal Slider, Gallery on Left and Gallery on Right. Elsewhere the theme lists Polylang and Loco Translate alongside WPML, RTL CSS, and translated front-end files for German, French, Spanish, Persian and Dutch.
The ThemeForest file list names PHP, CSS and JS files plus a PSD entry, and the vendor feature list separately mentions layered mockup PSDs, web font files and SVG/PNG icons. If a PSD source is part of your handoff, confirm what the PSD entry actually contains before you rely on it.
Questions & answers
Can I use Elementor instead of BM Content Builder?
The vendor states that ART supports content creation with Elementor and WPBakery Page Builder, so you are not locked to BM Content Builder. The caveat is in the demo data: the vendor says the demos are built with BM Content Builder, so an imported demo arrives as BM layouts you would rebuild in Elementor rather than convert.
Does the theme work without the bundled builder?
The portfolio list, project layouts, headers and font controls are theme features documented separately from BM Content Builder, and the vendor lists Gutenberg editor readiness plus Elementor and WPBakery support. Whether every module can be reproduced outside BM without code is not something the supplied material establishes, so test the specific layouts you need.
Can the portfolio grid show shop products?
Yes according to the vendor: the portfolio list can source items from WooCommerce products as one of four options, alongside single posts, portfolio posts and the media library. The changelog shows repeated WooCommerce compatibility updates, which suggests the shop side is actively maintained rather than left at its first release.
