Overflow

The Demo Switcher is a re-skin tool, not a fresh start

Nine demos ship in one theme, and Code Supply Co. describes their signature feature as a Demo Switcher that applies a different demo at any time without affecting your content. Read that literally: the layout and styling change while your posts, pages and media stay put. That is the claim that makes the demo count more than a chooser you use once at setup.

Importing demo content is described as a separate, optional step suited to a brand-new blog, and the vendor says a switch does not leave you with piles of duplicate dummy posts and pages. For a site with a year of publishing behind it, that distinction is the one to plan around: change the design, keep the archive.

Treat it as a vendor description rather than a guarantee. A demo switch still touches menus, widgets and template parts, so the sane check is a staging copy carrying your real plugin set. Nothing in the marketplace listing reports that testing.

How the featured grid picks posts

The featured posts section is the theme's other area of real control. The vendor lists the sources you can draw from: filter by category, tag or specific post IDs; order by date or by view count; and set a time frame that limits how far back the selection reaches.

Those options describe a homepage you curate without republishing anything. A magazine running a themed week can point the grid at one tag and a narrow date range, then widen it again. An editor who wants the biggest stories rather than the newest can order by views, provided the Post Views Counter plugin the vendor also supports is counting them.

The companion switch is small and practical: excluding featured posts from the main archive in one click. If the same article appears in the featured grid and again at the top of the list below it, the homepage reads as a repeat. The toggle removes the second appearance without a second category to maintain.

Sub-category filters for content-heavy archives

The vendor also adds a filter on category pages, letting readers narrow a category by its sub-categories. It is listed as an option rather than a default, and it makes sense where one section carries a lot of posts: a style category split into fashion, interiors and beauty becomes browsable without building three separate landing pages.

This matters more than a decorative extra for a magazine with a deep category tree, because it saves the reader from scrolling long mixed lists. Sites with shallow categories can leave it off.

Three header types, and colours that follow your background

Posts and pages can use three different page header types. One places the header over an image with an overlay; another divides the header into columns, which the vendor says suits portrait and square preview images. That column version is the more unusual choice, since most magazine headers assume a wide landscape crop.

Colour handling has a similar automation: choose a dark background for the header or footer and text and links switch to white without a second setting. It saves fiddling in the Customizer at the cost of predictability — you get white or the default, not a mid-tone you pick by hand.

Content slots for ads and subscribe forms

Under "Additional Content," the vendor describes inserting content into template parts without editing template files or overriding templates with a child theme. The examples are concrete: an ad spot under the header, a short description above the featured posts section, a subscribe form below post content. Banner snippets and AdSense placement are handled the same way, from the Customizer, in predefined locations.

That differs from a widget area. Widgets land where the theme registered a sidebar; these are fixed positions in the page structure you fill from the settings side. It removes the child-theme step for a newsletter block or a banner, but the positions are the vendor's, not ones you define.

The sidebar has its own behaviour. Widgets can stick while scrolling in two modes: to the bottom edge of the sidebar, or to the top edge of the last widget. The second is aimed at an ad placed as the final widget, keeping it in view through a long article. The vendor says this uses native sticky positioning and does not flicker on tablets and phones, including on mobile — a vendor claim, not an observation.

Navigation follows the same one-click logic with three settings: show the menu only when scrolling up, keep it sticky always, or turn stickiness off. The scroll-up option buys viewport on mobile at the cost of hiding navigation on the way down.

Powerkit is a separate plugin, not an invisible theme layer

Share buttons, social links, author and about widgets, newsletter opt-in forms, sliders and tiled galleries, a lightbox and lazy loading come from Powerkit, which Code Supply Co. describes as their in-house plugin rather than part of the theme. The pitch is that you skip shopping for compatible plugins for those basics, and that modules can be disabled individually — the part that matters if you audit page weight.

Share buttons specifically can sit before post content, after it, or in the floating post sidebar, with the priority networks ordered first and four colour schemes.

The realistic expectation is a separate plugin with its own release cycle and settings screen. Whether a module overlaps awkwardly with a newsletter provider or gallery plugin you already run is the kind of thing to settle before building.

Declared platform support, read with care

The marketplace attributes, recorded on 5 November 2026, list WordPress 6.6.x through 7.0.x and mark Gutenberg Optimized as Yes, with compatibility declared for the Block Editor, Elementor, WPML, Contact Form 7, Gravity Forms and Facebook. The vendor separately names Polylang alongside WPML for multilingual sites, and Co-Authors Plus for guest and multi-author bylines.

Two caveats keep this honest. These are declarations from the listing, not the results of installing the theme on a particular host. And naming Elementor says the theme is expected to work alongside it; it does not mean the demos are built in it, and the theme's own options live in the native WordPress Customizer, where the vendor says every setting previews live before you save.

The vendor also claims no CSS framework dependency such as Bootstrap, a limited set of generated thumbnail sizes, Retina-ready assets, built-in RTL support, a .pot translation file and Yoast breadcrumb styling. The package file list names PHP, CSS and JavaScript; there is no design source file among them.

What the record does not settle

The listing's version figure and the version of any archive you obtain are different things, and runtime behaviour on your PHP version, caching setup or ad network's script bears directly on the sticky sidebar and the featured-grid queries this theme is built around. Those are settled on a staging install, not from a feature list.

If your homepage depends on curated, filtered featured posts and your team wants to change the design without rebuilding content, the two features to judge first are the Demo Switcher and the post-source controls. Everything else — headers, sticky behaviour, Powerkit modules — is easier to adjust afterwards than a homepage structure that does not fit.

Questions & answers