Aviana

Treatment menus built from dedicated elements

Most themes leave you to build a treatment menu out of text blocks and hope the spacing holds. Aviana's vendor feature list names a Price List shortcode and a separate Pricing Table shortcode, which suggests two different display jobs: a running list of treatments with prices beside each entry, and a boxed table for comparing packages or membership tiers. For a day spa, those are usually the two most-linked pages after the homepage, and having them as purpose-built elements means the alignment and typography come from the theme rather than from manual markup.

The same list includes Product Info, Product List and Product Carousel shortcodes. Those are the shop-facing elements, so a candle range or a retail shelf of oils can appear inside a page you assemble in WPBakery rather than only on WooCommerce archive templates. That is the distinction worth understanding: the shortcodes handle display inside your own page layouts, while WooCommerce handles the cart and checkout behind them.

The vendor description does not spell out what settings each shortcode exposes, so treat the names above as a map of what exists rather than a specification of how configurable each one is.

Who appears on the page, and how

A therapy or aesthetics practice sells on people as much as on treatments. Aviana lists Team List, Team Member and Team Slider shortcodes, giving three ways to present practitioners: a grid-style listing, an individual profile block, and a slider for the carousel treatment many service sites use on the homepage.

Social proof has its own elements too. A Clients Carousel shortcode covers the logo strip of partner brands, press mentions or accreditation badges, and an Interactive Banner shortcode is listed as a way to build a clickable promotional panel — useful for a seasonal offer or a gift-card push without composing the block by hand.

The description names these elements without describing their layouts, image ratios or field sets, so the practical way to judge them is to look at the imported demo pages that use them.

Section composition: full-screen, split, uncovering

Beyond the individual content elements, Aviana offers section-level tools: Full Screen Sections, a Vertical Split Slider and an Uncovering Sections shortcode. Each changes how a visitor moves through a page rather than what a page says. Full-screen sections normally suit a short, deliberate sequence — arrival, treatment intro, booking prompt — while a vertical split slider keeps two panels in dialogue and an uncovering section reveals content as the visitor scrolls.

Those choices come with build costs. A page made of full-screen sections needs copy that fits a viewport, and a scrolling reveal works against a visitor who wants the price list in two seconds. Aviana also lists parallax images in sections, video and image backgrounds, variable grid size, anchor functionality for one-page sites and smooth page transitions. The anchor option is the one that pairs naturally with a section-driven homepage: a menu that jumps between blocks suits a practice with a small number of clearly defined services.

The vendor markets these as composition options. Whether a given demo uses them, and how they behave on a phone, is not something the description answers.

Header choices that suit different service menus

The feature list names four header types: Standard, Minimal, Centered and Vertical. Read as a set, they cover quite different site shapes. A centred header gives a spa brand a symmetrical, editorial first screen; a minimal header keeps a large hero photograph unobstructed; a vertical header puts persistent navigation down one side, which suits a long treatment menu better than a horizontal bar with a dozen dropdowns.

Supporting that, Aviana lists a Full Screen Menu option and multiple header behaviours, plus optional separate logos for the mobile header, for light and dark header versions, and for the sticky header. Widget areas are equally granular: header top, header bottom, mobile header, sticky header, side area, full-screen menu and footer, along with the ability to register custom widget areas. If a practice wants opening hours in the header top strip and a booking phone number in a sticky bar, those slots exist.

The scope of this section is broad, and the honest summary is that Aviana gives you many places to put things rather than prescribing one arrangement.

The plugin question, and the declared versions

The vendor description states that WPBakery Page Builder and Slider Revolution are included, and even assigns values of $46 and $26 to them. That is a vendor claim about the product as sold on the marketplace. The marketplace's own file list, by contrast, records only PHP Files, CSS Files and JS Files — no bundled plugin folders are named there.

Both statements can be true at once: bundled plugins frequently arrive through a separate installer or the theme's own dashboard rather than as folders inside the theme archive. Still, if the bundled builder matters to your build, confirm what your package actually contains rather than assuming the inclusion sentence covers it.

Compatibility is declared in the marketplace fields as observed on 4 November 2026: WordPress 6.5.x through 7.0.x, WooCommerce 9.x.x and 10.x.x, WPBakery Page Builder and WPML, with Contact Form 7 also listed in the feature description. Those are declarations recorded with the listing, not results from running Aviana on your PHP version, host or plugin stack.

What the changelog says about upkeep

The release record is unusually continuous for a theme first published years ago. The latest entry, version 2.3.1 dated 14 January 2026, updates Mikado Core to 1.7.2, refreshes the Google Fonts list and improves PHP 8.3 compatibility. The release before it, version 2.3 from 27 December 2025, adds WooCommerce 10.4.x compatibility and updates WPBakery Page Builder to 8.7.2 and Revolution Slider to 6.7.40.

Earlier entries show the same pattern across 2025 and 2023: each release usually moves the bundled builder and slider forward, adjusts the core plugin, and touches WooCommerce compatibility. For someone planning a build now, that record says the theme is actively kept in step with the plugins it depends on — which matters most if you rely on the bundled builder and slider rather than your own copies.

It also means the theme's behaviour is tied to a moving set of components. If you install Aviana on a stack newer than the top of the declared version range, a staging test is the sensible first step.

Fonts, child theme, and the limit on demo imagery

Typography is handled through theme settings rather than hard-coded stylesheets: the description lists 800+ Google Fonts, highly customisable typography settings, and separate typography settings for responsive breakpoints. Paired with seven icon font packs, that covers the visual layer of a spa brand without editing CSS, and a child theme is included for anything the settings do not reach.

The limitation to plan around is the photography. The vendor states plainly that it does not own the copyright to the images used in the theme's demos, that they exist for presentation only, and that they cannot be used on your site unless you license them from a stock library yourself. Wellness and spa design leans heavily on calm imagery, so budget for that licensing or a photographer before the site goes live — the visuals in the demo are the one part of the package you cannot simply keep.

Questions & answers