907

Pages that do not have to share one identity

Most themes treat the logo, colours and type as site-wide settings. The vendor's feature list for 907 describes something more granular: pages can have their own logos, colours, fonts, menus and more. The same pattern appears in the loader entry, which says CSS page loaders can be enabled or disabled on a per-page basis.

That changes what kind of site this is good for. If you are building one brand with one tone across every URL, per-page overrides are extra settings you will never touch. If you are building a site where a campaign landing page, a client case study and a portfolio piece need to read differently while sharing one installation, the overrides are the reason to pick the theme.

The per-page menu assignment is the piece that makes this practical. If a landing page can carry its own logo but is stuck with the main navigation, the illusion breaks. 907's menu list covers menus that can be set on any page, post, portfolio item and so on, which is what lets a section stay visually and structurally separate.

WPBakery is claimed in the package; Elementor is listed as compatible

The vendor's feature list says the theme includes WPBakery and Revolution Slider. Elementor and Elementor Pro appear in the marketplace's compatible-with attribute, alongside WooCommerce 6.x.x through 9.x.x, WPML and the listed browsers.

Those two statements are not the same commitment. A bundled builder is part of what you receive; a compatibility entry says the vendor reports the theme works with software you install separately. The changelog supports the first reading more clearly than the second: version 5.3.17 records updates to WPBakery 8.7.2 and Revolution Slider 6.7.41, and earlier releases repeat the pattern with WPBakery 8.5, 8.2, 8.0.1, 7.9, 7.7.2 and 7.4.

Elementor's record is thinner but present. Version 5.3.14 carries a "BUGFIX: Elementor loading issue" entry. If your team has standardised on Elementor, that bugfix tells you the route is maintained without telling you it has been tested against every Elementor release.

The marketplace attributes, recorded on 3 November 2026, mark Gutenberg Optimized as No. That describes whether the theme's design system was built around the block editor. It does not turn the block editor off, and it does not mean a page cannot be written in blocks. It does mean the theme's own layout controls are documented through the two builders above.

Boxed or full width, per page

The vendor lists a boxed and full width option, a full width menu bar option and a full width footer area option. Read together with the per-page styling, these are the settings that decide whether a page looks like part of the main site or like its own microsite.

A full-width menu bar and a full-width footer are usually the difference between a page that feels contained and one that runs edge to edge. Where the vendor places the boxed/full-width choice is not spelled out in the supplied description, so if a specific page needs one and the rest needs the other, verify that in the theme options before you build the layout around it.

Page loaders belong in the same category. A loader on a media-heavy landing page can cover the moment before images settle; a loader on a fast text page is a delay people notice. Being able to switch it per page means you can make that call without a plugin or custom code.

Repeating portfolio and blog loops on one page

The vendor's phrasing is "Unlimited Portfolios, even on same page" and "Unlimited Blogs, even on same page." The operative part is the second clause. A theme that gives you one portfolio grid per page forces you to choose between showing selected work and showing everything; multiple loops on one page let you run a featured row at the top and a full filterable archive underneath.

Each loop carries its own controls. Portfolios are described as filterable, with optional AJAX pagination, and with excerpt text and titles that can be shown or hidden. Blogs offer optional AJAX pagination or a load-more button, plus the same show/hide controls for titles and excerpts. Those toggles matter more than they sound: a title-free thumbnail grid and a titled list are different pieces of furniture, and having both on one page requires the loop to carry the choice.

Portfolio items also support mouseover video, so a project tile can play a clip on hover instead of relying on a still. Version 5.3.9 added video autoplay to the portfolio gallery grid, which extends the same idea to grid view.

Menus, sidebars and the structural side

Multi-level navigation is listed, and menus are unlimited and assignable across content types. Unlimited sidebars sit alongside them. Together they give you the ability to keep a section navigable on its own terms — a course page with a syllabus sidebar, a portfolio section with a project-type menu — without building a second installation.

Blog posts get a next/previous navigation with three styles listed. That is a small detail until you have a long-form blog where the end of an article is otherwise a dead end.

WooCommerce support is described with ajax pagination and an animate-to-cart feature, and version 5.3.10 added a theme option to enable or disable the cart icon in the menu. If the shop is a secondary part of the site rather than the point of it, that cart-icon switch is a real convenience.

Starting from 27 demos and 134 blocks

The vendor lists 27 included demos with one-click import and 134 theme blocks. The demo range is deliberately broad — the description names trades and professions from aerial photography and architecture to bakeries, gyms, law firms and salons — which tells you the demos exist to show range rather than to sell one vertical.

That breadth is worth treating as a menu, not a template pack. A demo import brings a starting state, and because 907's design decisions can be per page, an import can leave you with a set of pages whose logos, fonts and menus already differ from one another. Decide whether you want that variation before you import, and whether you are building on the demo or replacing its look entirely.

The 134 blocks are the raw material for the replacement path. They are what you assemble pages from once you have picked a starting point.

What the update record suggests

The changelog runs through version 5.3.17 with a steady cadence. The recurring entries are bundled-plugin refreshes — WPBakery and Revolution Slider version bumps appear in most releases — plus occasional functional additions such as the WooCommerce cart-icon option and portfolio video autoplay.

What this supports is a narrow claim: the vendor keeps the bundled tools current and fixes reported problems, including the Elementor loading issue in 5.3.14. What it does not support, and nothing in the supplied description should be read to support, is a statement about how the theme performs on your host, how long support runs, or whether every demo imports cleanly in your environment.

The marketplace attributes, observed on 3 November 2026, list WordPress 5.0.x through 6.9.x and the browsers Firefox, Safari, Opera, Chrome and Edge. Those are vendor compatibility statements. WPML appears as a compatibility entry, so a multilingual build needs its own WPML licence; language files in po/mo format are listed separately.

Questions & answers