Loud

Playlists as a manager, not just a player embed

Two separate lines in the vendor's feature list sit side by side: an "Advanced Playlist Manager" and support for embed players from Spotify, Soundcloud, Mixcloud, Bandcamp, Reverbnation and similar services. They solve the same display problem in different ways, and Loud keeps both available.

A managed playlist is built inside the theme, so the ordering, the sequencing and the presentation belong to you rather than to a streaming platform's widget. An embed hands playback and play counts to the service, which keeps streaming numbers where listeners already are. A label releasing a sampler can run it as a managed playlist while individual records point at their Bandcamp or Spotify players.

The distinction is worth settling before you build, because it decides where your audio actually lives and which pages carry which kind of player.

Discography, releases and events are separate objects

The vendor describes discography layouts in metro, grid and column arrangements with hover effects, multiple customizable layouts for single release items, and a separate event set covering list, grid and sidebar layouts plus a single event page that carries the event's details.

That structure matters more than the individual layouts. An album and a gig are different things with different fields, so a new record is not a post filed under a category, and an upcoming show does not share a stream with a news item. A tour page can exist as tour dates, and a record can exist as a release, without either borrowing the blog's shape.

It also changes how much planning the site needs. Decide whether a release page is a one-record landing page, a campaign hub that changes over a few weeks, or a permanent catalogue entry. The theme offers layout options; the content model behind them is your call.

There is also a video post type, described as having multiple layout options and a preview that plays on hover — a small but telling detail for a site whose homepage is likely to lean on moving images.

Tracks and releases that point at the shop

Among the vendor's WooCommerce claims, the one that stands out is the ability to link your tracks and releases to WooCommerce products. Around it sit a shop with multiple layout options, multiple customizable single product page layouts, an AJAX cart and a wishlist.

The link is the useful part for a band or label selling physical editions. A vinyl pressing, a deluxe bundle or a ticket tier can live as a product, while the release page that promotes it stays a release page — one points at the other instead of the music content being pushed into the store. Readers who arrive from a record page land on the right product rather than a general shop listing.

The marketplace attributes, observed on 4 November 2026, declare WooCommerce 10.x.x and Contact Form 7 compatibility alongside WPBakery Page Builder. Those are declarations of what the vendor targets, not a record of the combination being exercised on your install.

Editing happens in WPBakery and Slider Revolution

Loud includes a tailored version of WPBakery Page Builder that the vendor says adds a set of elements aimed at musicians, and Slider Revolution with 10 demo sliders. Page layouts are assembled in WPBakery; banners and hero sequences are built in Slider Revolution.

The marketplace listing marks Gutenberg Optimized as No. Read that as a statement about how the designed templates and elements are built: your layout work will happen in the page builder, and a site planned around hand-composed block layouts would work against the theme's design rather than with it.

Because both plugins carry their own editing interfaces and their own release cycles, maintenance is not only about theme updates. Keeping builder pages and slider content current when either plugin moves forward is the part of the job that outlasts launch.

Navigation and reusable sections sit above that layer. The vendor lists 9+ menu layouts with styling options, a mega menu, a sticky menu and several header layouts, plus Content Blocks for building headers, footers and sections you can repeat. For a label with artists, releases, tour dates and a store to expose, the menu depth does real work; for a festival site, a reusable line-up strip defined once and placed on several pages saves rebuilding it.

The demo artwork is stripped from the package

The vendor's note is explicit: the credited artwork — album covers, photo manipulations, logo sets — appears for presentational purposes only and is replaced by placeholder images in the theme package. Reusing any of it on a live site requires permission from the individual designer named in the credits.

For a music site this is a larger constraint than it sounds, because cover art and artist photography carry most of the visual weight. Importing the demo gives you spacing, structure and typography, and grey placeholders where the striking imagery sits. Judge whether the layouts suit you only after you have your own photography and cover art in place, and budget for both.

The package file list includes PSD files, which is where the designed graphics can be adapted rather than simply swapped out. Other declared package contents are PHP, CSS and JavaScript files.

The vendor also lists a child theme, responsive and high-resolution output, 9 widget areas, and WordPress 7.0.x support. Those are vendor and marketplace declarations observed on 4 November 2026, not results from testing your installation.

Questions & answers