AJAX browsing, and the switch that turns it off
Airtifact's vendor describes the theme as AJAX driven and then adds the detail that matters for anyone planning a build: you can disable the feature with a single click in the panel. That combination is unusual. Themes that lean on AJAX transitions for project pages usually treat it as part of the design, not something you can turn off.
So the decision is not just aesthetic. With AJAX loading active, moving between project items keeps the visitor in a continuous browsing flow rather than reloading a fresh page each time. That suits a portfolio where the work is meant to be scanned in sequence. Turning it off gives you conventional page loads, which is what you want if analytics, third-party scripts or caching layers on your install depend on each page arriving as its own request.
The vendor does not describe what changes on the back end when you flip that switch, so test it on a staging copy before you commit to one behaviour across a large body of work.
Two navigations: regular and compact
The feature list names two navigation treatments — a regular one and a compact one — without mapping either to a specific screen size. In practice that gives you a choice between a full-width menu that can carry the brand and a tighter version for sites where the project grid should own the top of the page.
The changelog adds context on the compact menu, which was patched in version 1.3.0 for an indexing issue tied to submenu arrows. Cascading dropdown menus were added back in version 1.0.7. If your site structure runs three levels deep, those entries are the ones to read before assuming the compact menu handles deep hierarchies gracefully.
A small content builder, by design
Airtifact does not adopt a mainstream page builder. The vendor describes a custom content builder and stresses what it lacks: no bloated code, no unnecessary elements or components. That is a statement about scope — a smaller component set you arrange into project layouts, rather than an open canvas of blocks.
The builder's real dependency is the Advanced Custom Fields PRO plugin, which appears throughout the changelog as it was updated alongside the theme, most recently to 6.8.8 in the 1.3.3 release. ACF PRO has its own licensing arrangements separate from the theme, so confirm how the version bundled with Airtifact is licensed for your site before you plan around those custom fields.
If your team has standardised on a different editor, this is the point where Airtifact becomes a poor match rather than a matter of taste.
Grid engines, filtering and how much loads at once
Project layouts can use Packery, Isotope or masonry, according to the vendor. Those are different packing behaviours, and the choice affects how a portfolio with mixed landscape, portrait and square images holds together on a wide screen.
On top of the grid sits a filtering method for project items, plus the option to run several portfolio pages rather than one archive. That covers a common portfolio pattern: a filtered wall of selected work on the front page, and separate pages for individual disciplines.
Loading behaviour is a separate decision, and the vendor lists three routes — lazy loading described as a way to control infinite scroll, infinite scroll itself, and regular pagination. Infinite scroll keeps a visitor scrolling through the whole body of work; pagination gives you a predictable number of items per screen and a stable footer. The description does not say how the three are configured together, so treat the combination as something to verify in the demo.
Two blog styles, but only one at a time
The vendor is explicit about a limitation that other listings would leave you to discover: there are two blog styles, Minimal and Magazine, and only one style is possible on a site. The demo shows both by being tweaked for the purpose.
Read that before you promise a client a minimal journal alongside a magazine-style index. You are choosing between them, and the choice applies to the blog as a whole rather than to individual categories. The rest of the content layer — fullscreen backgrounds per project and section, hero sliders, self-hosted video — is described as configurable per item, which is where most of the design variance sits.
Type that adapts, and type you set by hand
Airtifact's vendor describes fonts that respond to browser size and adjust per device, with the option to override any of those sizes manually in the content editor. That is a useful middle ground: the theme handles the scaling, and you can still fix a specific heading that breaks at a particular width.
Type sources are the Google Fonts library plus a documented route for adding custom fonts, which was expanded with a Font Manager in version 1.0.6. The theme is also listed as localization ready with RTL support, so right-to-left scripts are covered by the vendor's claim rather than an add-on. The description does not name a translation plugin, and the marketplace listing does not declare WPML, so a multilingual build needs its own plan.
The custom framework and the theme-swap claim
Airtifact runs on Underscores, the WordPress starter theme, wrapped in the vendor's own framework. The vendor makes a specific claim about that framework: Airtifact and its sibling theme Calafate can be swapped for each other by changing options in the panel, without rebuilding the site.
That is worth treating as a vendor statement rather than a migration guarantee. Two themes sharing a framework can still diverge in templates and field groups, and the description does not detail what is preserved. If the swap is part of your plans — for instance, a portfolio version and a different presentation of the same work — confirm it on a copy of the site.
The marketplace listing, observed on 4 November 2026, records a responsive layout with 4+ columns, widget readiness, high-resolution graphics, and PHP, CSS and JS files in the package. Gutenberg Optimized is marked No, which describes how the designed templates were built rather than ruling out the block editor.
Maintenance history and the security entry
The changelog runs from the September 2018 release to version 1.3.3, dated 20 August 2026, which lists WordPress 7.1 and PHP 8.5+ readiness along with the ACF PRO update. The release before it, 1.3.2, carries the entry to read first: an important vulnerability fix, with the vendor recommending an immediate update.
That entry tells you two things. The theme has had a security issue patched, and the vendor's own guidance is that running an outdated copy carries risk — which is the reason to confirm which version you are installing rather than assuming it is current. Release notes are also the record of what changed, not proof of what was tested on your server. Evaluate the theme against the WordPress and PHP versions you actually run, and check how the ACF PRO dependency is handled in your setup.
Questions & answers
Can I use both the Minimal and Magazine blog styles on one Airtifact site?
No. The vendor states that only one blog style is possible at a time and that the demo was tweaked to show both, so the choice applies to the whole blog.
Does Airtifact need the block editor or a third-party page builder?
The vendor describes a custom content builder rather than Gutenberg or a mainstream builder, with ACF PRO underlying the custom fields. The listing marks Gutenberg Optimized as No, which describes how the templates were built.
What happens if I disable the AJAX behaviour?
According to the vendor, AJAX can be turned off with one click in the theme panel. The description does not specify which scripts or features change as a result, so test it on a staging copy if your analytics or caching setup depends on per-page loads.
