A header you configure per layout, not per site
Blade's vendor description spends its first stretch on the header, and the specificity is unusual. Four layouts are named: Default, Logo on Top, Side Navigation and Hidden Side Navigation, each with its own options. Then come six separate logo slots — default, dark, light, side navigation, sticky and responsive — plus sticky styles (Advanced, Simple, Shrink) and menu styles (Classic, Button, Underline).
The six logo slots are the detail worth pausing on. A single logo file that gets recoloured by CSS breaks down whenever the background behind it changes: a transparent header over a hero image, a dark sticky bar, a white mobile bar. Separate uploads per context mean you supply artwork that was drawn for each one instead of hoping one file survives every background. If your brand has a stacked mark, a horizontal lockup and a one-colour version, this is where they go.
That design is aimed at sites where the header is part of the pitch — corporate and creative portfolios where a side navigation or a transparent header over a full-width image is the point of the layout, not a fallback.
The per-item override is the real organising idea
Scattered through the vendor feature list is a repeated phrase: globally or per page, post, portfolio item, product. Header overlapping works that way, and so does the hidden menu navigation option. The sliding area is described as customisable differently per custom post.
Read together, those lines describe one mechanism rather than four tricks. A landing page can start with an overlapping transparent header; a product page can drop the menu for a distraction-free read; an individual project can carry its own sliding panel. You set a default in the options panel and then break it where the content needs it.
The cost is decision fatigue. Every one of those per-item controls is a field on an edit screen, and on a fifty-page corporate site somebody has to decide which pages earn an exception. If nobody owns that decision, you end up with a site whose header changes unpredictably from page to page — the same setting that makes a bespoke landing page possible also makes inconsistency easy.
Feature sections and backgrounds, with WPBakery underneath
Composition runs through WPBakery Page Builder (the vendor still uses its older Visual Composer name), with more than 40 elements built for the theme. The listed background section effects are numerous and named individually: default, parallax, parallax left to right, parallax right to left, animated, horizontal animation, and image used as a pattern. Sections can be full width, and feature sections can be custom or full height with a colour, image, slider, video or map.
Parallax appears twice in the vendor list — as a section effect and as a standalone smooth-parallax feature with vertical and horizontal variants and a sensor option for tuning performance. Treat the sensor setting as a hint about the real constraint: layered movement on a full-width section is the most expensive thing this theme does visually, and the mobile result depends on the device in front of the visitor.
Above the builder sits a Redux Framework options panel, reachable from a Blade tab in the WordPress admin. The styling layer includes a live colour customizer the vendor describes as unlimited, plus typography controls covering standard fonts and more than 600 Google Fonts, with responsive type control. The marketplace attributes also record Gutenberg Optimized as Yes; that describes the vendor's block-editor support claim, and it does not mean the WPBakery layer disappears.
The shop layer, and what the declared ranges cover
Blade's WooCommerce support is listed as a set of concrete behaviours rather than a badge: images that swap on hover in the shop overview, a zoom effect on the single product page, an Ajax cart, and title backgrounds, colours and height set separately per product category. That last item is the one that changes shop structure — a store split across categories can give each one its own header treatment without a plugin.
The marketplace attributes captured on 4 November 2026 declare WooCommerce 6.x through 10.x, alongside Contact Form 7, Gravity Forms, WPBakery Page Builder and WPML. They also record WordPress 5.2.x through 7.0.x and browsers from IE9 to Edge. Those are vendor declarations made on that date, not tests against a particular server, PHP build or plugin set, and a shop is where that distinction bites hardest — cart and checkout behaviour changes between WooCommerce major versions.
On languages, the vendor lists WPML compatibility with a certificate reference, Polylang support, translation-ready files and RTL support for Arabic, Persian, Hebrew and Urdu. If the site has to sell in more than one language, check the currency and checkout flow in the demo rather than only the translated pages.
Modes that need configuring before launch
Several listed features are switches a site sometimes needs and almost never notices after launch. Maintenance mode and coming-soon mode are built in, which means a pre-launch site does not require a separate plugin — provided you remember to turn them off. The theme also offers a one-page version and full-page scrolling, two layout modes that change how a site behaves rather than how it looks.
The translation of those modes into practice is where hidden work sits. Full-page scrolling, like the parallax effects, is a navigation model that suits a handful of sections and fights a long content page. A one-page build with a sticky anchor menu per page (another listed feature) is a sensible pairing; the same anchor menu on a conventional multi-page site mostly adds clutter.
Package contents are listed as PHP, CSS and JS files, with high resolution and widget-ready both marked. Theme imagery in the preview is stock licensed for demonstration, and the vendor notes that imported dummy data brings placeholders instead of those photographs — so the demo's photography is a design reference, not something the theme hands you.
Where the header system earns its keep
Blade appeals most to a project with a small number of deliberately different page types: a corporate site whose landing page opens on a transparent header, a portfolio where each case study sets its own sliding intro, a shop whose categories deserve their own title treatments. The static elements of the theme are less distinctive than the override logic, and WPBakery is a well-known editing environment you either already work in or deliberately avoid.
The unresolved question is maintenance discipline rather than features. With per-item controls for headers, menus, titles and sliding areas, the theme rewards a team that documents which page uses which override and why. Its maintenance and support terms are not verified here, and neither is runtime behaviour on your stack, so the vendor's demo is the place to test the header variants and the shop flow before you plan around them.
Questions & answers
Can I use a different header on individual pages?
Yes, according to the vendor description. Header overlapping and hidden menu navigation are both listed as applying globally or per page, post, portfolio item and product, and the sliding area is described as customisable differently per custom post.
Do I need separate logo files for each header style?
No upload is mandatory, but the theme provides six logo slots — default, dark, light, side navigation, sticky and responsive — so you can supply artwork drawn for each background instead of relying on one file to work everywhere.
Does Blade use the block editor or a page builder?
Page composition is built around WPBakery Page Builder with more than 40 theme-made elements, and global styling runs through a Redux Framework options panel. The marketplace marks the theme as Gutenberg optimized, which is a vendor support claim rather than a replacement for the builder layer.
