A review engine, not a rating field
Many magazine themes add a star average to the bottom of a post. In 15Zine the scoring system is documented as a full feature set: three score formats (stars, percent or points), an optional score subtitle under the final score, unlimited criteria, and unlimited pros and cons per review.
The setting that changes editorial practice is who votes. The vendor says a review can be editor-only, visitors-only, or both, so staff verdicts and crowd scores can coexist on one site, or be applied to different posts.
Reader voting is limited by a cookie with a value of "1" placed on the visitor's computer rather than by an account. That discourages a repeat click from the same browser; it is not a verified identity system, and a reader who clears cookies can vote again. If auditable reader scores matter to you, plan around that limit.
The same score data feeds a Top Reviews widget, which the vendor says can list top, latest or oldest reviews, scoped to a category or site-wide, with time filters.
How a scored post looks on the page
Each post chooses from seven featured image styles: standard, standard no-crop, full-width, screen-width, full-screen, parallax and slideshow. The vendor also documents an option to hide the header area inside a post so the chosen image style owns the top of the screen, which matters most on full-screen and parallax layouts.
Typography is settable per post, so one feature can carry a different font set from the rest of the site, and the vendor lists access to Google's font library plus recommended-font dropdowns. Featured images accept a photo or video credit line, and ordinary image embeds can be expanded to full-screen without shortcodes.
Format-specific handling extends the same idea. Galleries are described as accepting landscape and portrait images without cropping and opening full-screen; video posts can either replace the featured image or appear behind a play button overlaid on it; audio posts do the same and accept a Soundcloud embed or self-hosted MP3/OGG files.
Page-level controls include a left, right or no sidebar and an optional custom sidebar, so layouts can vary by article rather than by site.
Front pages are assembled from a fixed module vocabulary
The homepage builder is drag-and-drop but bounded. The vendor's list is specific: four grid modules showing three, four or five articles; four slider options (one image per slide, one full-screen slide, two images per slider, three images per slide); a grid-and-slider hybrid at three posts per slide; and a full-width slider for featured or latest posts.
That is the practical decision. You are arranging known shapes with background colours or images, not drawing a layout from scratch. If a front page needs a composition outside those shapes, the builder will not produce it.
For sites that lead with a stream of stories, nine blog styles cover the alternative, from standard, portrait, two-column and thumbnails through big and mixed treatments, plus variants opening with a full-screen grid of three or five. Every blog style can run normal pagination, infinite scroll, or infinite scroll behind a load-more button.
Categories get the same controls plus their own blog style, module choice, background and a colour picker that tints menu hovers and review boxes, which lets each desk carry its own accent. Custom sidebars are available per category and per page.
Trending and view counts depend on Jetpack
The vendor states plainly that two visible features need and use statistics from Jetpack's stats module: the trending megamenu, which surfaces the most popular posts of the moment, week or month, and the post view count. The popular-posts widget's ordering by views rests on the same data.
Treat that as a build constraint. With Jetpack installed, the trending menu and view-based sorting come with it. Without Jetpack, the mega menu still exists as navigation, but view-driven popularity data does not.
The surrounding editorial chrome is theme-side: four menu locations, a mega menu system, a sticky sidebar, and toggles for the author box, lightbox, next/previous box, byline and back-to-top button. The vendor's SEO notes describe a single H1 per page wrapped around the post title, alt text pulled from media data, and schema rich snippet microdata.
Shop and forum pages get their own settings tabs
WooCommerce and bbPress are handled as styled surfaces rather than a compatibility line. For the shop, the vendor describes a redesign to match the theme, a left, right or no-sidebar choice for full-width store pages, a background colour or image for shop pages, and a dedicated WooCommerce widget area under Appearance → Widgets.
bbPress gets a comparable tab: a global forum colour, the same three sidebar positions, background colour and image, a settable sticky-post colour, and its own widget area.
Login With Ajax modals and widgets are described as integrating with bbPress so signed-in members see quicklinks for profile, subscriptions, favourites and replies, keeping forum users out of the WordPress admin. These are vendor descriptions of styling and option coverage; they say nothing about how a specific WooCommerce or bbPress release will behave on your server.
What the compatibility record does and does not settle
The marketplace listing observed on 3 November 2026 shows the latest version as 3.3.9.8, with the vendor's last update recorded in December 2021. Declared software support runs from WordPress 4.9 through 6.5.x, and the vendor's own summary describes a v3.3 line on WordPress 6.2+ and PHP 8.0. Declared browser support covers Chrome, Firefox, Safari, Opera, Edge and IE11.
Compatible plugins are listed as Elementor and Elementor Pro, WPML, Jetpack, Contact Form 7, Aesop Story Engine, bbPress 2.5.x and 2.6.x, WooCommerce 5.x through 7.x, and the Block Editor, with Gutenberg Optimized marked Yes. Files included are PHP, CSS and JS; the vendor says a child theme ships ready to use and a dummy-content XML replaces all demo photographs with a placeholder image.
A declared range is not a record of testing against every release it names, and the gap between the 2021 update and later WordPress versions in that range is worth weighing. If your project runs a newer WordPress or PHP build, confirm behaviour on a staging copy before committing the design work.
Questions & answers
Do the trending menu and view counts work without Jetpack?
No. The vendor says both the trending megamenu and the post view count need the statistics from Jetpack's stats module. Without Jetpack you can still run the theme's mega menu, but view-based popularity ordering is unavailable.
Can a site run staff reviews and visitor ratings side by side?
Yes. Review mode can be editor-only, visitors-only, or both. Reader votes are limited by a cookie rather than an account, so a fresh browser or cleared cookies allow another vote.
Is the homepage builder required?
No. Nine blog styles cover front pages that lead with a stream of latest posts, each with normal pagination, infinite scroll or a load-more button. The builder's grids, sliders and hybrid module are for front pages built from those fixed blocks.
