TheFox

The real decision is which of 18 headers and 10 footers you start from

TheFox's marketplace description spends much of its space on counts, and the counts that matter most on a business or corporate site are the structural ones. The vendor lists 18 header designs, with an optional top bar whose contents you choose, plus sticky and transparent header states. Footers come in 10 layouts with a 1–4 column widget arrangement and an optional bottom bar. Site layout switches between wide and boxed in the options panel.

That is a different proposition from a theme that ships one header and asks you to restyle it. Each of the 18 is a finished arrangement — mega or standard menu, with or without a top bar, sticky or transparent — so picking one is closer to choosing a starting position than building from scratch. The transparent header is also selectable per page, which lets a landing page sit over a hero image while the rest of the site keeps a solid bar.

Where the menu stops helping is anything the vendor did not design. Nothing in the description suggests you can invent a nineteenth header arrangement from the panel; the variation lives inside the set. If your brand needs a header structure outside those layouts, plan on template work rather than a settings change.

Home pages follow the same logic. The description promises 20 pre-designed home page layouts, more to come, and pairs that with one-click demo import so a demo's pages arrive instead of being rebuilt by hand. Between 20 home options and 18 headers, the early part of a project is mostly selection.

Visual Composer is included; the 35 modules are where the theme's own work sits

WPBakery Page Builder — called Visual Composer throughout the vendor copy — is described as part of what the theme provides, and the vendor states that everything visible in the demo is assembled from its modules. The decisive number is 35: modules built by the theme author, covering blog, portfolio and team listings as Ajax modules, plus WooCommerce display.

That sets the editing model. You compose pages by dragging these modules into the builder and adjusting their style and colour, rather than by writing templates. The vendor also states that colour customisation extends to all the modules, which is what keeps a many-page site from looking assembled from mismatched parts. Module styling is also where the counting stops being impressive and starts being useful: 35 blocks reuse the same colour controls, so a palette change reaches the whole composer set.

One listing detail deserves care. Elementor appears in the compatible-with attribute, but the description presents Visual Composer as the tool that ships and builds the demo. A compatibility entry is a vendor statement that the theme works alongside a plugin; it is not a documented page-building path. Treat WPBakery as the route the theme was built around.

The block editor is a separate question. Gutenberg Optimized is marked No, which describes whether the theme's design system is organised around blocks. It does not remove the editor from your installation; it says the theme's own layouts were not built for it.

The mega menu answers the problem of a site with many sections

Multi-purpose themes usually fail on navigation first. A corporate site with services, team, portfolio, blog and shop outgrows a flat dropdown quickly, and the built-in mega menu addresses that directly: 1–5 columns, icons assignable to individual menu items, widget support inside the panel, and colour controls for the dropdown.

Widget support is the detail with the most practical weight. A column can hold something other than links — a short contact block, a recent-post list, a service description — and that content is managed in a widget area instead of being hard-coded into the menu. Five columns also let you split a large section tree into parallel columns rather than one long vertical list.

The build is only as good as your menu structure. Nothing in the listing supplies the information architecture; the theme provides the container and the styling, and you decide how many sections earn a column each.

The shop is composed from product modules, not a separate storefront design

WooCommerce support here is described in the language of the builder: 1–4 column product display options, custom modules that render products, custom layouts for shop and single-product pages, and WooCommerce shortcodes available inside the composer. Product queries can run by category, SKU, on-sale status, featured status or newest arrivals.

That matters when products are one section of a business site rather than the whole site. A category row on the home page, a featured strip on a services page and a full product archive can all come from the same module with different queries, instead of leaning on one shop template to do every job.

The compatible-with attribute lists WooCommerce 6.x.x through 9.x.x, while changelog entries running to 12 March 2026 record WooCommerce 10.x support. Those are vendor statements about intended compatibility, not results from a test on your installation. If the store is central to the project, run a product page and a cart flow on your own setup before launch.

Five blog layouts, five portfolio layouts, and pages that can break the frame

The vendor lists five blog layouts — Classic, Multi-author, Grid, Masonry and Timeline — each able to run with a left or right sidebar or full width, with ten overlay effects and a choice between classic pagination and a load-more button. Portfolio gets a matching five layouts, with grid and Packery arrangements, 1–6 column options and category selection per portfolio page. Team members add three layouts and nine designs, with categories per member page.

Read alongside the page-level options, these counts describe a site whose sections need not look identical. Per-page controls assign a slider, place it above or below the header, switch to a transparent header, set a custom title bar colour and background, hide breadcrumbs, and choose a left or right sidebar. A single portfolio page can carry a slider under a transparent header while the blog index stays conventional.

One caution on the loop layouts: the description presents multiple blog and portfolio pages as separately configured instances, each with its own category selection. That is a statement about what you can set up, not a promise that changing one page's configuration updates the others.

What the compatibility record covers, and what stays with you

The marketplace attributes, observed on 3 November 2026, list WordPress 5.0.x through 6.9.x. The most recent changelog entry, dated 12 March 2026, records WordPress 6.9.4 compatibility together with updated Slider Revolution and WPBakery builds and WooCommerce 10.x support. Read as a whole, the changelog is mostly bundled-plugin refreshes with periodic WordPress and WooCommerce version lines — a maintenance-shaped record rather than a run of new features. That is plausible for a theme this old, and it says nothing about how the current release behaves with your plugin stack.

The file list includes Layered PSD alongside PHP, CSS and JS files. The PSDs are design source, not part of the running theme: useful if you want to adapt the theme's artwork in a design tool, irrelevant if you never open Photoshop. The description also notes a basic child theme, which is where changes belong that the options panel cannot express.

Two things stay genuinely open before you commit. The description does not say whether the bundled builder arrives as a separately licensed plugin or as theme-included tooling, and that affects how you handle updates. And with 20 home layouts spanning business, portfolio, blog and shop directions, the import itself matters: confirm that the demo you choose includes the inner pages your project needs, not only a home page.

Questions & answers