Static Site Support

Sites built with Bricks can be easily exported as static sites with tools such as Simply Static. The vast majority of BricksExtras features are now compatible (v1.7.7+) to be used on these static sites, aside from the user/e-commerce based features.

Static Mode

To make it easier to work with, in the BricksExtras settings there’s a new Static support mode (v1.7.7+). Enabling this disables the few features that wouldn’t be compatible for a static site in one go (and removes them from inside Bricks settings). It also amends a few features with static-friendly alternatives. This way you can then confidently proceed in building the site without accidentally using a feature that later wouldn’t be compatible when exported.

So, with static mode enabled..

The disabled features are..

• WooCommerce conditions
• Member conditions
• User / Current Date based conditions
• Favorites / Wishlists
• Styler for WPGridbuilder’s facets
• The ‘token expiry’ feature for Bunny videos. (static tokens would expire)

The amended features are..

• Calendar AJAX popup – If intending to export to static, don’t use the AJAX setting in Bricks popup template when attaching to the calendar element, as this requires WordPress. For displaying the event details inside of the popup.. use the new static-friendly x_popup_event dynamic tags, which can be set up to show data from the clicked events live without needing AJAX. Any dynamic data from posts can be attached to these in the calendar settings.
• Header search – Replaces the inner form with the form provided by your chosen static exporter. (Simply static can replace the form input with a Fuse live search, which can be styled from the header search settings). The existing live search option will be hidden, as this relied on Bricks AJAX search.
• Toasts Queuing – With static mode enabled, the PHP side of triggering toasts is disabled, but all built-in triggers and interactions are available.
• Interactions – All available apart from the interactions for Fluent Form & WS Form submissions/failures won’t trigger. Bare in mind Bricks’ own Form, Query AJAX and Filter triggers also won’t trigger.

Things to Consider

Brick’s native features such as the filter elements and live search can’t be used on static sites, due to them using AJAX (and obviously any WooCommerce based elements/features)

BricksExtras features has all been tested with Simple Static plugin, but we’ll also be adding support for other WP to static export solutions, including of course if Bricks adds in there own native solution.