Known limitations
Theme and local examples
The gallery, slideshow, feature images, color variants and content rules have actual demonstration pages. The existing blog articles, other examples and global settings were not changed for them. Different image captions do not prove that the original photos are different.
The selection rules are provided by Content Blocks. In this version, earlier simple Particles selections are also processed through its compatibility integration; the plugin must therefore remain enabled. Drafts and unapproved pages must not appear merely because their taxonomy matches.
Custom font files must actually be configured. The gallery requires the bundled local JavaScript for the full-size view; without JavaScript, all images remain accessible as normal links. Paused autoplay does not silently start again.
External services
Stock photo searches, AI generation and translation require a deliberate action while signed in to Admin2. These examples contain no actual search jobs, image generation jobs or machine translations.
AI Horde does not guarantee availability or waiting times. Custom AI providers must actually support the implemented contract. There is no automatic image editing, no unauthorized replacement of files and no silent paid fallback service.
Google Cloud Translation is the default provider, but remains unavailable until an operator-provided API key is configured. A monthly free allowance does not mean the service is generally free. The multilingual website structure, target languages and human review remain the operator's responsibility.
Embeds require consent for each item. This theme does not make non-public videos, documents, arbitrary external iframe addresses or a live X feed available. Google Maps and Google Docs require an actual configured public embed URL.
What the demonstration establishes
The pages illustrate the implemented functionality and identify configuration that is still required. They neither prove that provider jobs have already been run nor promise compatibility with every third-party device or future provider version. The optional legacy plugin integrations still have their own requirements.