Developer Overview

This document is the orientation page for developers and integrators who work with ADP Car Market Hub. It deliberately stays at a high level. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation.

When to use this document

Read this document if you are:

• A site implementer who needs orientation before customising templates or settings for a specific dealership.
• An integrator wiring the plugin to a CRM, marketing tool or external scheduler through the plugin's documented supported surfaces.
• A reviewer evaluating the plugin at a high level before recommending it.

End users (dealership staff configuring the plugin from the WordPress admin) should start with the user-facing sections of the documentation instead, in particular the user handbook and admin reference.

What the plugin is

ADP Car Market Hub is a WordPress plugin that imports and synchronises vehicle listings from an upstream marketplace into WordPress, and exposes:

• A public vehicle catalogue (archive, single vehicle page, comparison page, favorites, search filter).
• An admin area for configuration, imports and lead management.
• A small set of documented shortcodes and theme-overridable templates that integrators can rely on.

The plugin requires the WordPress and PHP versions declared in its plugin header. It ships with bundled translations for the supported locales and provides a clean activation, deactivation and uninstall path.

How to navigate this section

• For environment setup, see Local Development Setup.
• For coding conventions, see Coding Standards.
• For supported integration surfaces, see Shortcodes For Developers and Template System And Overrides.
• For translation contributions, see Internationalization For Developers.
• For contribution process, see Contribution Guidelines.

Other pages in this section provide a public-safe summary of areas (architecture, storage, REST/AJAX, cron, security, release, analytics, Market Insights, etc.) whose internal details are deliberately not published.

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.