Custom Post Types And Taxonomies

This page describes the plugin's content model at a high level. Internal post-type slugs, taxonomy slugs, capability maps and meta-key inventories are implementation details and are not published here.

Content model at a glance

• The plugin stores vehicle listings and contact leads using WordPress's native content storage.
• Vehicles can be classified using vehicle-related taxonomies provided by the plugin.
• The vehicle catalogue is presented through the plugin's bundled templates (overridable from a theme — see Template System And Overrides) and through the documented shortcodes.

For integrators

Use the documented shortcodes, theme template overrides and the admin UI to work with the plugin's content. Do not depend on specific post-type or taxonomy slugs from external code; treat the content model as an internal detail of the plugin.

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.