A sermon is a record, not a blog post with an audio link
The marketplace description lists "Audio/Video Support for Sermons" as a feature, and the changelog shows what that means in practice. Sermons hold media files, and the list widget can display icons for video, audio and PDF versions; a fix in version 3.9 stopped those icons appearing "even when files are not available." Version 1.7.3 changed sermon file downloads to save with only the file name.
So a sermon entry is closer to a media record than a post. It can carry an audio file, a video file and a PDF, and each one is offered to visitors separately. If your church publishes a weekly recording plus a notes document, that structure saves you from pasting players and links into post bodies and hoping the layout holds.
Speakers and series sit alongside it. Version 1.8 added a speaker image and name to the header of the sermons-by-speaker page, which implies speakers are their own taxonomy rather than a line of text in the body. Series information was adjusted on single sermons in 1.6.1, and version 2.6 added the option to sort sermons by their own sermon date in category and tag templates. That last detail matters more than it sounds: published date and delivery date are rarely the same, and an archive sorted by the wrong one reads out of order.
The description also names touch and swipe support for sliders, which applies to whichever slider you place above a sermon rather than to the sermon player itself. Worth checking on the demo if you publish long recordings.
Events carry a schedule the theme has to reason about
The feature list names FullCalendar for the events view, an events listing page, and an upcoming events countdown timer. The changelog is the better guide to how much scheduling logic sits underneath.
Recurrence is not just weekly. Version 3.8.1 added recurring frequencies for every two weeks and every year. The patches around it show the edge cases that come with that: an earlier build fixed a missing first instance for weekday recurrences, and a follow-up in 3.8.1.1 fixed the same class of problem. If your calendar includes a midweek group that meets fortnightly or an annual commemoration, these are the releases that matter.
Version 3.2 added an option to mark an event as online, which hides the location links. That is a small setting with a clear editorial use: a streamed service or a Zoom prayer meeting should not display an address and a map pin it does not have.
Filtering and counts are handled as options rather than assumptions. Version 3.8.2 put a hide-past-events setting into the shortcode builder so a calendar can show only what is upcoming. Earlier releases fixed the countdown timer showing an incorrect time to the event, and 2.5 fixed an event preview showing a register link when registration had been switched off. The vendor describes the events listing page as a separate template, so you are not limited to a calendar grid.
The Core plugin split, and the switch that turns the post types off
Version 2.3 introduced an AdoreChurch Core plugin to hold the theme's functionality, described in the changelog as a way to clean up the theme and improve performance. Almost every release since then lists a Core plugin update. Read that as a maintenance signal: the parts that define a church site are developed as an extension rather than buried in template files, and they get updated alongside the theme.
Version 2.8 added two settings that follow from the split. One disables the theme's built-in event and sermon functionality. The other lets you change custom post type settings.
Why would a church turn its own sermons off? Sites that already run a separate sermon podcast plugin, or a congregation page that shares a multisite network with another ministry site, sometimes prefer one source of truth. Having the switch documented is more useful than having to comment out code. If you do use it, confirm what happens to existing entries before switching, since the changelog does not describe whether sermon data is preserved or hidden.
Version 2.7.2 added admin columns for the event and sermon post types, and version 2.8's custom post type settings suggest slugs and labels are configurable. Neither is a headline feature, but both reduce the friction of publishing every week.
Colours, layout widths and galleries around the content
The vendor's feature list puts the design controls in conventional territory: 12 prebuilt colour schemes with unlimited colour options, boxed and wide layouts, seven gallery page types, and Isotope-based galleries with sorting. Version 3.5 changed the colour scheme option field to an image selector, which is a usability change rather than a new capability.
The gallery count is the one to plan around. Seven gallery layouts means the decision is about how photographs are presented, not whether they can be. If your site leans on images from services, camps or community events, that variety is the practical part of the theme; if it does not, most of the gallery set will go unused.
Sliders arrive through two bundled plugins the vendor names: Revolution Slider and Layer Slider, both credited in the description and both appearing repeatedly in the changelog. They are described as included items with the vendor's own valuation attached. Treat those valuations as the vendor's statement about the ThemeForest package, not as a claim about any particular download.
Compatibility is a declaration; the block editor question is separate
The marketplace attributes, observed on 3 November 2026, list WordPress 5.5.x through 7.0.x, WooCommerce 6.x through 10.x, bbPress 2.5.x and 2.6.x, and WPML. Those are vendor and marketplace declarations of tested ranges, not the result of running the theme against your PHP version, caching layer or plugin set.
The same record marks Gutenberg Optimized as No. That attribute describes whether the theme is built around the block editor, and it should not be read as proof that the block editor is unavailable to you. Pages here are assembled with the theme's own page builder elements and shortcodes, so the editing model you get is the theme's, with Gutenberg as an adjacent tool rather than the centre of the workflow. If your team has standardised on block patterns, confirm how they behave before committing.
The WooCommerce range is worth a second look only if you plan to sell something: books, event tickets through a shop product, or merchandise. The theme declares support; it does not describe a shop design of its own.
What the package declares
The vendor's file list for the ThemeForest item names Layered PSD, PHP, HTML, CSS and JS files. The PSD is the unusual entry for a WordPress theme and is relevant if a designer is working from the same layouts.
The description also states plainly that images from the live preview are not included in the template. Church sites are photography-heavy, so budget for your own shoot or licensed stock rather than expecting the demo imagery to travel with the theme. The credits name DollarPhotoClub and CreationSwap as image sources for the preview.
Questions & answers
Can I use Adore Church if another plugin already manages my events?
Version 2.8 added an option to disable the theme's built-in event and sermon functionality, so the custom post types can be switched off. The changelog does not explain what happens to entries you have already created, so confirm that before disabling on a live site.
Do sermons support both audio and video in one entry?
The vendor lists audio and video support for sermons, and the sermon list widget can show icons for video, audio and PDF files. Version 3.9 fixed those icons appearing when the files were missing, which suggests each media type is tracked separately per sermon.
Does the theme need WooCommerce installed?
No. WooCommerce is listed as compatible, not required. The marketplace description frames the theme around church, charity and non-profit content, with WooCommerce relevant only if you want to sell something.