Benqu

The part of Benqu that isn't about the homepage

Plenty of news themes sell a grid. Benqu's vendor feature list includes two items that only matter once a reader is inside an article: Ajax infinite scroll for post details, and a reading progress bar.

Those change the reading session rather than the front page. A visitor who reaches the end of a story can continue into the next one without a page reload, and the progress bar gives a sense of how much remains. For a site built on repeat visits and long sessions, that is closer to the actual job than another hero layout.

The changelog puts both on a timeline. Post details Ajax infinite scroll appears in version 1.0.5, and an on/off control for the infinite scroll followed in 1.0.6 — so the behaviour is a setting you can switch, not a fixed part of the theme.

Advertising, counts and related posts as theme settings

The same vendor list names an Ads Manager and a social counter, plus post views and related posts. Version 1.0.4 of the changelog adds an AdSense code field in the theme options, and 1.0.5 records an Ajax cart count.

The per-post controls developed through the 1.0.8 line are worth noting because they let you decide what a story page shows: view count, date and comments each got enable/disable options, then author, comments and related posts followed with hide/show switches. If your editorial policy is to publish without a byline, or without comment threads on some sections, those are options rather than template edits.

Treat all of this as the vendor's description of the theme's controls. It tells you what settings exist, not how the ad placements look on your own pages.

News sections built as Elementor widgets

Version 1.1.15, dated 7 March 2026 in the changelog, added a set of section types aimed squarely at news front pages: Hero Grid, News Featured, News Grid, News Split, News Ticker, Homepage Hero and Content Boxes. An earlier release, 1.1.12, added a Benqu Post Article Slider widget.

Because these are widgets, the vendor's framing is that a homepage is assembled from parts you place and configure in Elementor — a ticker strip, a featured block, a split layout — instead of choosing one fixed demo and living with it. The vendor counts 100+ custom Elementor widgets and 12+ different home pages, including demos named for niches such as newspaper, gaming, food, mental health, photography, illustration and pet blog. Widget totals are the author's own figure and are not independently verified here.

The practical question is not whether the count is impressive but whether the section types match how you present stories. A ticker and a split layout imply different editorial rhythms, and both are described as available.

The site-wide shell: options, RTL, dark mode, child theme

Site settings run through the Codestar Framework, which the vendor lists alongside the Elementor workflow. Version 1.1.13 added separate colour options for the header, menu and top bar, and 1.0.4 added footer background colour, top-bar date visibility, a login button toggle and an option to hide or show the cookie notice.

Full RTL support is listed as a feature and appears in the changelog as an addition in 1.0.1, with an Owl Carousel RTL fix recorded in 1.1.4. A dark/light mode switcher is also listed, with a default dark-mode option added in 1.0.9. A child theme was added in 1.0.6, which matters if you plan template overrides you want to keep across updates.

The vendor's compatibility list reads as boundaries rather than bundled software: WP User Frontend, Breadcrumb NavXT, Contact Form 7, Elementor, One User Avatar, MC4WP Mailchimp, SVG Support and WooCommerce, plus the theme's own Benqu Extension for its core add-ons. The theme is built on Bootstrap 5.x per the vendor attributes and on the Underscores framework.

Compatibility claims versus the release history

The stored marketplace attributes, observed on 4 November 2026, list WordPress versions from 5.6.x to 7.0.x, WooCommerce 6.x.x, Elementor and Elementor Pro, Bootstrap 5.x, Gutenberg Optimized as Yes, and included PHP, CSS and JS files. Those are listing-level claims, not the result of installing the theme on your host.

The changelog is the more granular signal. It records tested compatibility with 6.3 and 6.6 at the points those releases shipped, a PHP 8.2 function update in 1.1.8, and an Elementor deprecation fix in the 1.0.8 line. Where the two disagree, or where a version range looks broader than the release notes, verify on a staging copy rather than assuming either field alone settles it. Nothing here is a record of current runtime testing.

What the news sections and shop claims don't settle

Two things stay open after reading the vendor material. The first is whether the news section widgets — ticker, hero grid, featured, split — are general-purpose enough to use on category archives and landing pages, or are designed mainly for the demo homepages. The description presents them as home page components, and the vendor's live demo is where that becomes clear.

WooCommerce appears both in the compatibility list and in the changelog as an addition in 1.0.1, with template version updates in 1.1.3. That history says the shop templates are maintained; it does not say the theme configures a shop for you. If a store is part of the plan, the product pages you rely on are the ones to check.

Benqu suits a publication whose pages will be assembled in Elementor and whose readers spend time inside articles, with advertising, view counts and byline controls managed from theme settings. If you need your design to follow from the block editor, the listed Gutenberg Optimized value is a starting point for a look at the demo, not a description of the demo's construction.

Questions & answers