Artemis

A changelog that keeps WooCommerce templates current

Release notes for shop themes usually mix marketing additions with housekeeping. Artemis's recent entries are almost entirely the second kind, and that is the most useful thing to know about it. Consecutive releases record WooCommerce template files being refreshed against new plugin versions, with Slider Revolution and WPBakery Page Builder bumps alongside them, the latter reaching version 9.0.1 in the entry dated 18 October 2026.

Those aren't the same thing as headline features, but they matter more for a shop than they do for a brochure site: WooCommerce changes its template markup between versions, and a theme that stops following those files drifts out of step with the plugin. A changelog weighted toward template refreshes suggests the vendor treats that upkeep as the job.

This describes the vendor's version history. Which build a given copy carries is a separate question you settle inside WordPress, not from the changelog.

Elementor with theme widgets, and section templates in the library

The vendor describes Elementor support that goes past compatibility. Artemis widgets were rebuilt for Elementor, later extended with new options (the Artemis Products widget) and joined by a gallery grid widget. Its section templates are described as reachable directly from the Elementor library, so a saved band can be dropped into a page and edited there instead of being rebuilt.

One changelog entry is worth noticing for day-to-day editing: custom content width was enabled for single product pages built in Elementor. If you plan to art-direct a product page rather than accept the default WooCommerce arrangement, that is the setting you would otherwise work around.

WPBakery Page Builder is listed separately as included. The vendor does not say that every demo exists in both editors, so if a specific demo layout is the reason you are buying, confirm which editor built it before committing a team to one workflow.

The Lookbook widget, and the shop it implies

The Lookbook Elementor widget, described with different layout options, is the most specific item on the vendor's list. It points at a shop merchandised by styling — image and products together — rather than by specification grids. The related gallery grid widget added later supports the same kind of page.

A lookbook only earns its space if you have editorial photography and a reason to group items by outfit or scene. On a catalogue where shoppers arrive already knowing what they want, a filtered grid does the job and costs less upkeep.

The changelog offers one detail about how the feature behaves in practice: an entry records a fix for lookbook display on mobile devices. Multi-item layouts that collapse to a single column are where this kind of widget usually shows strain, so check your width breakpoints against your own image count.

Shop controls: product layouts, dynamic sidebar, wishlist, minicart

Under the builders, the vendor exposes e-commerce choices as settings. Different product page layouts means the single product screen isn't fixed; a dynamic shop sidebar means the category and filter column draws from the catalogue, so adding a category doesn't require a second edit.

Wishlist and minicart rounds out the browsing loop — save for later, and keep the basket visible while shopping. Quick view appears in the changelog as something fixed for related products, which tells you it exists as a listing-page behaviour.

All of this comes from the vendor's feature list and release notes; nothing here has been exercised on a live store. Wishlist is the one to check against variable products and stock status, since that is where saved-item features tend to need handling the vendor doesn't describe.

Per-page backgrounds, colour schemes and menu styles

The multipurpose label rests less on the builders than on page-level appearance controls: an individual background image or colour for each page, a changeable full-screen background, unlimited colours through the customizer, and dark or bright colour schemes. Menu styles are switchable from theme settings, and a split-menu style was added along the way.

The practical use is a store running different moods side by side — a campaign landing page, an editorial lookbook page, a plain category index — without building three separate templates. The trade-off is that consistency becomes your responsibility; the theme supplies the levers, not the art direction.

A smaller addition worth knowing about: a customizer option for a mobile-specific logo, which lets the desktop mark stay detailed while a simpler version carries small screens.

Content pages, translation and design sources

Beyond the shop, page templates cover blog, contact, wishlist, a blank page intended for Elementor and a page with sidebar. The contact template carries an Ajax form, and the blog page offers different layout styles. Translation readiness is stated with .po/.mo files included, and WPML appears in the compatibility attributes — useful if the storefront has to run in more than one language, though a multilingual WooCommerce build is worth testing end to end rather than trusting the attribute.

The marketplace file list records PHP, CSS, JS, a PSD and a Layered PSD, so design sources travel with the theme. They're for adapting layouts or producing matching assets, not for running the site.

Compatibility attributes observed on 4 November 2026 list Elementor, Elementor Pro, WooCommerce 8.x through 10.x, WPBakery Page Builder and WPML, over a declared WordPress range from 5.8.x to 7.0.x. Those are declarations, not a published test matrix. Gutenberg Optimized is recorded as No, which speaks to the theme's design intent and to where its custom blocks live, not to whether the block editor works.

Questions & answers