A sub-header that is built, not styled by hand
Magazine homepages usually treat the header as one unit: logo, menu, and whatever else the vendor packed in. The Issue's changelog records a Sub-Header builder in version 1.4.0, released alongside two new post grid styles, one post block grid style, three article styles and a widget style. That grouping suggests the strip beneath the navigation is composed as its own region rather than inherited from the header.
The practical value shows up when the front page and an article need different things in that band. Version 1.6.5 added options to display language flags there, and 1.6.4 fixed the Subheader Full Width option. The full-width setting is the one that decides whether the strip runs edge to edge or aligns with the content column, so it is worth deciding against your layout early rather than patching it later.
Loop filters that stop one story appearing everywhere
A magazine front page is mostly repeated post queries, and the theme's Post Source attribute gained two controls in version 1.5.3: ignoring sticky posts, and excluding chosen tags and categories. Those matter on a page with several blocks, because a pinned announcement or a busy tag otherwise shows up in the lead slot, the secondary row and the sidebar rail at once.
Related Articles took a different route. Version 1.5.5 added the option to build them from categories, so the strip under an article follows the section you filed the story in rather than a looser tag match.
Both are per-block settings. Two grids on the same page can carry different exclusions, which is the point — a lead block and a rail rarely want the same pool.
Dark mode as a stored preference, with its own logo
The theme's dark mode was revised across several releases rather than shipped once. Version 1.4.2 added separate logo options for dark mode and made dark/light changes persist between page changes; 1.5.1 and 1.6.3.2 carried further fixes and improvements; 1.6.1 added a theme option to place the toggle in the mobile menu.
Two of those details affect day-to-day reading. A stored choice means a reader is not flipped back to light on the next article, and a second logo means the mark can be drawn for a dark background instead of sitting on a colour it was never designed for. The mobile toggle is the smaller item that decides whether a phone visitor can reach the switch at all.
The changelog also records a fix in 1.6.0.1 for the accent colour not applying in some areas, so how far the palette extends beyond the logo and accent setting is not something the supplied evidence settles. Check the theme options if colour control is a deciding factor.
Translation and a language switcher are separate jobs
Language handling splits in two places, and mixing them up costs time. The theme declares WPML compatibility, and version 1.5.3.2 added a wpml-config.xml file — the file that tells WPML which theme strings and options should be translatable. That covers the theme's own text.
The subheader language flags from 1.6.5 are a display option, a visible switcher placed in the strip under the navigation. A bilingual magazine needs the translation configuration and the switcher; having one does not give you the other.
Social plumbing follows a similar release-by-release trail: WhatsApp added in 1.6.5, Flipboard sharing in 1.4.1, LinkedIn in 1.2.2.7, TikTok embed support in 1.6.3.3, plus repeated fixes to Twitter and Facebook sharing. Those entries describe the theme's own sharing buttons and embeds, not a guarantee for every network.
WPBakery is maintained, and it is not the only editing route
WPBakery Page Builder appears in the compatibility attributes, and the changelog shows it patched regularly, including a conflict fix in 1.6.3.1 and updates in the most recent entries. Some features were delivered through it: version 1.6.2 added dropcap support to WPBakery Text elements inside articles, a typographic detail that only reaches pages built on that element.
The marketplace attributes also record Gutenberg Optimized as Yes, and one changelog line mentions a fix to an Elementor Products element. Read those as declared routes rather than a statement about the demos — nothing in the supplied evidence says which builder the demo pages use. If your team has a standard editor, inspect a demo page before committing.
What ships with the theme
The files-included attribute lists Layered PSD, PSD, PHP, CSS and JS. Layered sources are useful when a designer has to rebuild a banner or promo panel to fit your masthead instead of tracing it from a screenshot. The vendor states plainly that demo images are not licensed for reuse and would need their own licences.
The compatibility list is broad for a magazine theme: WPML, bbPress 2.5.x, Easy Digital Downloads, The Events Calendar and its Pro version, Gravity Forms, Contact Form 7, WooCommerce 6.x through 9.x, WPBakery Page Builder and Foundation 6. Each is a declaration that the theme works alongside the plugin. It does not make any plugin required, and it says nothing about how deeply the theme styles that plugin's output.
WordPress support is declared from 5.5.x through 6.8.x, with Widget Ready marked Yes and documentation marked well documented. The most recent changelog entries record a vulnerability fix, WPBakery updates, a compatibility pass for the latest PHP and WordPress releases, and a demo import fix.
Questions & answers
Do the post filters apply across the whole site?
No. The ignore-sticky-posts and exclude-tags-and-categories options added in 1.5.3 belong to the Post Source attribute of an individual block, so each grid or list on a page can be filtered differently. That is what lets a lead block and a sidebar rail draw from different pools of stories.
Is the dark mode choice remembered on the next article?
Version 1.4.2 of the changelog states that dark/light mode changes persist between page changes, and the same release added separate logo options for dark mode. The option to place the toggle in the mobile menu was added later, in 1.6.1.
Does the theme need WPBakery Page Builder to work?
The supplied evidence does not say the theme requires it. WPBakery appears in the compatibility attributes and is updated throughout the changelog, and some features — such as dropcap support in article text elements — were built for it. The marketplace also records the theme as Gutenberg optimized, so more than one editing route is declared. Which builder the demo pages use is not stated, so check that in the demo if your team must standardise on one editor.
