Plugin Architecture For Developers

This page gives a high-level, integration-oriented overview of how the plugin is organised. Detailed internal architecture, class wiring, bootstrap sequence, long-lived collaborators and capability/option/cron identifiers are maintained separately and are not part of the public documentation.

High-level overview

ADP Car Market Hub is a self-contained WordPress plugin that imports and synchronises vehicle listings from an upstream marketplace API into WordPress. It registers a vehicle content type, exposes a front-end catalogue (archive, single page, comparison, favorites, search filter), and provides an admin area for configuration, imports and lead management.

The plugin follows standard WordPress plugin conventions: it boots from a single PHP file on plugins_loaded, ships translations under /languages, and provides clean activation, deactivation and uninstall paths.

What integrators should rely on

• The plugin's settings UI for all configuration.
• The published shortcodes for embedding catalogue, comparison, search filter, favorites and seller location blocks (see Shortcodes For Developers).
• Theme-level overrides for the bundled front-end templates (see Template System And Overrides).
• Standard WordPress extension mechanisms (filters/actions/REST/post-meta) only to the extent documented in the public extension-point pages of this section.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

• The plugin admin settings UI.
• The documented shortcodes.
• Theme-level template overrides as described in Template System And Overrides.
• The general Developer Overview for orientation.

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.