A black theme where the homepage names are the specification
Most multipurpose themes list a count of demos and leave the rest to a preview tour. Luxa's pack list names all twelve homepages: Creative Studio, Design Agency, Photographer, Product Page, Portfolio carousel, Freelancer, Shop One Screen, Categories, Split Screen, Packery Portfolio, Left Menu Portfolio and Grid Portfolio.
That naming is more informative than a number, because it splits the set into two kinds of decision. Four entries answer who is publishing: a design agency, a creative studio, a freelancer, a photographer. The rest answer how work and offers are arranged. If your site does not sit in one of those four roles, the first group stops being relevant quickly; the second group still applies.
The black base is the other defining choice. On a dark canvas the accent colour and the photography do most of the visual work, which is why the vendor's easy colour management claim carries more weight here than it would on a light theme.
Portfolio arrangements: carousel, Packery, left menu, grid
Four of the twelve homepages exist to present project work in different shapes. A carousel moves a visitor through projects one or a few at a time. Packery uses a packing layout that mixes tiles of different sizes rather than forcing one column width. The left menu variant puts navigation in a side panel so images run beside it. The grid variant is the most conventional and the most predictable.
Beneath those homepage variants, the vendor lists unlimited custom portfolio pages, so a project index does not have to match the opening arrangement. Two gallery layouts are named separately: grid photo gallery and masonry photo gallery. The grid suits a set shot at consistent framing; masonry accepts mixed aspect ratios without cropping everything to one shape, which is usually what a photographer wants when a shoot includes vertical and wide frames.
The changelog gives the portfolio one concrete behaviour change. Version 1.1.0 replaced the filtering mechanism with Ajax loading, so filtering projects no longer reloads the page. If filtering is central to how you browse a large project library, that is the entry to look at first.
Commerce and video without a full store build
Shop One Screen and Home Categories are homepage variants, not a completed shop. They suggest where shop content can sit on a landing page: a single-screen presentation, or a category-led entry point. What the theme provides is that starting layout; the products, prices and checkout come from WooCommerce itself.
The marketplace compatibility attributes, recorded on 4 November 2026, list WooCommerce 5.x through 10.x. Those are declared claims from the vendor snapshot, not results of independent testing. If a specific WooCommerce release matters to your store, verify it against the build you hold rather than reading the range as a guarantee.
Video is claimed for YouTube, Vimeo and MP4. The practical distinction is between embedding a platform link and hosting a file on your own server; MP4 support matters for the second case, while YouTube and Vimeo cover the first. Supporting pages come along too: a coming soon page, a custom 404, a contact form and two blog layouts, one of them fullscreen.
Unyson, the Luxa Dashboard and how you will edit
Luxa runs on the Unyson framework, per the marketplace attribute. The changelog for version 1.1.0 added a Luxa Dashboard, which points to theme settings being gathered into one theme-specific panel. On a dark theme that panel is where you would expect the accent colour and the layout switches to live.
The listing marks Gutenberg Optimized as No. That label describes how much the theme is tuned for the block editor; it does not prove the block editor is unavailable on your site. What it does tell you is that the author is not selling this as a block-first design system. If your workflow depends on block patterns or a block-based builder, Unyson's own option and page framework is a different way of assembling pages, and that difference is worth settling before you build layouts.
RTL support is listed by the vendor, so an Arabic or Hebrew build is on the table rather than an afterthought. WPML also appears among the compatibility attributes — a starting point for a multilingual portfolio, not proof that a two-language site arrives configured.
Images you must supply, and what else ships
The vendor states plainly that the theme does not contain all the images in the source zip file. On a photography and video theme this is the caveat that most affects your first impression: the preview's impact comes from its photographs, so the layouts will look different once real, licensed work replaces the demo set. Budget for both the imagery and the rights to use it.
The marketplace package description lists layered PNG, PHP, HTML, CSS and JS files. The stated minimum PHP version is 5.4, and the theme is described as responsive and retina ready with high-resolution assets. Marketplace attributes also name WPBakery Page Builder, WPML, Bootstrap 4.x and 5.x, with a WordPress range running from 4.9.x to 7.0.x. A listed integration does not mean every demo depends on it, and no compatibility list promises behaviour on a release that lands afterwards.
One maintenance detail belongs here rather than in the feature list. The vendor's update note says the license must be reactivated after a theme update, which makes updating a supervised task on a live site rather than something to leave running in the background.
Questions & answers
Are the demo photographs included with Luxa?
Not all of them. The vendor's notes say the theme does not contain all the images in the source zip file. Plan to supply your own photography and the licences that go with it, and expect the portfolio layouts to read differently once they do.
Does Luxa work with the block editor?
The listing marks Gutenberg Optimized as No, which is an optimisation label rather than a statement that blocks are switched off. The theme is built on Unyson, so pages are assembled through the theme's own framework and options.
What happens to the licence after a theme update?
The changelog entry for version 1.1.0 states that you should reactivate the licence after updating. Treat updates as scheduled work on a live site, not an unattended background process.
