Brook

A layout catalogue grouped by the industry you are building for

ThemeMove does not present Brook as one signature design. The vendor describes more than 30 homepages split into four named groups, and those names are the fastest way to judge fit. Multi-area covers Creative Agency, Digital Agency, Business, Design Studio, Architecture, Start-ups, Minimal Agency and Freelancer. Creative covers One-page, Landing App, Service, Product Landing, Shop, Presentation and Indie Musician. The portfolio group runs from Creative and Minimal through Vertical Slider, Vertical Slide Gradient, Full-screen Slider, Masonry and two Full-screen Hover styles. Gallery & News collects Masonry Gallery, Photo Slider Gallery, Grid Blog, Metro Blogs, Portfolio Slide, Minimal Metro Grid and Vertical Menu.

That structure tells you the theme expects you to start from a demo close to your sector and then customise it, rather than composing pages from an empty canvas. The product title leans towards agencies, but the vendor's own grouping covers architecture studios, musicians and shops, so treat the name as a starting point rather than a limit.

The counts stop at a headline, though. The description names styles without documenting what each one exposes in the settings panel, so the honest test is whether the layout closest to your content already looks like your content.

Blog and portfolio layouts are separate systems

Three figures sit side by side here and describe different things: six post formats for posts, more than 21 premade blog layouts, and more than 22 portfolio layouts.

The separation matters for a studio or agency site that publishes both project case studies and occasional news. Each collection gets its own set of listing arrangements, so a portfolio grid and a journal feed can be styled independently instead of inheriting the same template. The six post formats add a second axis on the blog side: one listing layout can carry a video post and a standard text post, which is how a demo stays varied while your own publishing cadence continues.

What the vendor does not document is how configurable each layout is once installed. The count is a menu of starting points, not a promise of per-layout options.

Footers chosen per page, edited in one place

The theme ships more than 16 premade footer styles according to the vendor, each built from its own combination of background, colour and typography settings. The mechanism is the part worth planning around: you pick a page's footer from a drop-down in that page's Page Options, and you edit the footer style's contents from a Footer section in the admin dashboard.

That two-step split has practical consequences. One site can close a services page with a dense link block and a one-page landing with a slim contact strip, without a second template. Because edits live in the dashboard's Footer section, changing a style updates every page that uses it — useful for consistency, less useful if you wanted one page's version to drift.

Headers are mentioned in the same part of the description as a separate collection of prebuilt styles, but without a published count. Judge those on the demo and treat the footer number as the firm one.

One-page sites and the Classic Mode requirement

Brook includes one-page homepages; the vendor points at the Product Landing demo as the example. The description draws a deliberate line between one-page scrolling and infinite scrolling: the first keeps a visitor inside a single document, moving between its sections, while infinite scrolling loads more content from a feed as the reader goes, or through a Load More button.

For anchor navigation, the vendor gives a specific instruction: create the one-page menu by switching to Classic Mode and setting menu items to point at each part of the page. If your team works mainly in the block editor, that is a mode change on the pages that need anchor menus, and it belongs in the build plan rather than being discovered mid-launch. The compatibility field marks Gutenberg Optimized as Yes, but that field does not tell you how the one-page menu is assembled.

Separate navigation controls — smooth scroll, a go-to-top button, pagination, an off-canvas menu and a light gallery — are grouped under Appearance > Customize, so these are site-wide settings rather than page-level ones.

What the shortcode library is actually made of

The shortcode section of the vendor description is the most concrete part, and it carries an inconsistency worth noticing. It opens with 80+ custom shortcodes, then itemises 60+ theme-built shortcodes, 22 default shortcodes and 13 WordPress widgets. Those parts do not add up cleanly, so use the itemised breakdown when you are planning pages and treat the 80+ figure as a headline.

The named theme shortcodes are the building blocks of a typical agency or studio page: progress bar, contact form, accordion, blog, icon, gallery and heading. The default set is structural: row, text block, section, separator, tour, tab, call to action and video player. Anyone who has used WPBakery will recognise the second group; the first is what Brook contributes on top.

The practical consequence is that page construction happens inside the builder's element panel. A call-to-action band or a progress-bar row is placed and filled in, not hand-coded. For a team without a developer that is the whole editing routine; for a team that prefers blocks or hand-written templates, this is the point where Brook's workflow diverges from yours.

WPBakery, Slider Revolution and where the bundling claim ends

The vendor lists WPBakery Page Builder, Slider Revolution, Font Awesome Pro and the WPBakery Page Builder Clipboard add-on, putting the combined value at up to $147. These are vendor statements about the marketplace product; the marketplace's own file field records PHP, CSS and JavaScript files without naming plugin folders, so nothing in that field confirms which bundled items appear in any particular copy.

Of the four, the Clipboard add-on is the one that changes daily work: the vendor describes copying or cutting single elements and stacks of elements between pages without leaving the builder interface, which is what you want when a section built once has to appear on six other pages. WPBakery is the structural centre of the build, since the shortcodes above live inside it, and Slider Revolution handles slider composition alongside it.

The vendor addresses licensing directly in a note: the plugins are described as integrated into the theme and usable from the admin dashboard without activation or a key, and anyone who wants an activation key is told to buy the individual licence from the plugin authors. That separates using the bundled copy from holding a licence for it — a distinction to settle with your client before launch rather than after.

Shop templates, and what the compatibility field does not prove

The marketplace compatibility field lists WooCommerce from 5.x through 10.x as observed in November 2026 — a stored declaration, not a test on your stack. Within that support the vendor describes two styles for a single shop page: Shop, which introduces featured items, offers and sale pricing, and Product Landing, which is built to present one new product.

The Product Landing style is the more distinctive of the two: a full-width presentation page for a launch, campaign or pre-order. The vendor also mentions add-to-cart, wish-list and compare buttons on product views, keyword, tag, filter and category searches, and Instagram feed displays. Those depend on WooCommerce extensions and third-party services named in the feature list rather than shown working in any archive.

If you need a shop that functions rather than one that is styled, the WooCommerce range in the listing is a declaration to verify on staging.

Demo import: additive, and cleanup is manual

The importer runs from Insight Core, through Import and then Import this Demo, with a notification when it finishes. The vendor is explicit about how it behaves: importing adds the demo content to the site rather than replacing what is already there, and removing it afterwards means deleting the imported content by hand.

That makes the first import a decision, not a step. Run it on a fresh install, or accept a manual cleanup job later. The same section of the description points to a tutorial video series covering the theme's setup, which is the better place to look for the click-through sequence.

Beyond the importer, the description makes general claims about responsiveness, clean coding, retina-ready imagery and SEO work. There are no figures behind those, so they read as positioning rather than product information, and the demo is where layout quality and rendering get judged.

Questions & answers