Orravo, Abuja Digital Studio

Loading strategies

Pick under Settings -> Loading strategy. The chosen value becomes part of the loading_strategy setting and selects which JS bundle ships to the page.

Strategy	Bundle	When to use
`monolithic` (default)	`assets/js/orv-fx.js`	One file, all modules. Smallest mental overhead
`split`	`assets/js/orv-fx-core.js`	Core only, packs attach as dependents
`lite`	`assets/js/orv-fx-lite.js`	Bare-minimum runtime for the lightest modules
`modern`	`assets/js/orv-fx-modern.js`	Targets evergreen browsers, smaller bundle
`packs`	`assets/js/orv-fx-core.js`	Same core as split, plus per-pack on-demand modules

Reduced motion

The reduced_motion_override setting decides how Orravo FX responds to prefers-reduced-motion: reduce:

auto - honour the user's OS setting (the default and the recommendation)
always - assume reduced motion regardless
never - ignore the OS setting (use sparingly; some users need it)

Conditional load

Flip Conditional load on to strip the FX <script> and <style> tags from any page whose rendered HTML buffer contains no data-orv-fx / data-orv-mag markup. Saves a request on pages that don't need motion.

CSS scroll-driven path

When prefer_css_scroll is on, Orravo FX adds ofx-css-scroll to <body> and the @supports block in orv-fx.css lights up. Modern browsers do scroll work in pure CSS; JS modules bail out, saving the rAF cost.

Designer mode and CSP

designer_mode exposes extra inline controls for Customizer + block-editor previews
csp_strict removes any inline event handlers from the runtime so a strict Content-Security-Policy with no unsafe-inline keeps working