Documentation · Developer Documentation

Frontend Assets

This page covers front-end asset loading at the integration level only. Specific asset file paths, script handles, dependency lists and localisation payloads are implementation details and are not published here.

High-level behaviour

The plugin enqueues its CSS and JavaScript on the front end only on pages that actually render plugin content (the vehicle archive, the single vehicle page, the comparison page, and any post or page that contains one of the plugin's shortcodes). Cache-busting is tied to the released plugin version so visitors always receive a consistent matched set of assets.

For theme developers

To style the front-end output, override the bundled templates from your theme (see Template System And Overrides) and add your own theme stylesheet rather than depending on the plugin's internal CSS class structure or asset handles. Internal asset handles, script dependencies and CSS selectors may change between releases.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

Internal class names, option keys, database tables, REST and AJAX endpoints, cron hook names, capability and nonce identifiers, and release / update infrastructure are treated as implementation details. They may change between releases without notice and are not part of the public integration contract.

Stability and change policy

Anything not listed as a supported public surface above is considered an internal implementation detail. Internal APIs, storage layout and security implementation may change between releases. Do not depend on them from third-party code, themes or external systems. Direct database writes are not supported.

Public documentation notice. This page provides a high-level integration overview only. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation. Supported integration surfaces are the documented shortcodes, template overrides, settings UI and any extension points explicitly published in this section.