Documentation · Developer Documentation

Admin Assets

This page covers admin-side 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 own CSS and JavaScript on its own admin pages only. The plugin does not assume the presence of any particular CSS framework beyond WordPress core admin styles, and it does not register itself on admin pages other than its own.

If you are styling the WordPress admin from a separate plugin or a custom admin theme, treat the plugin's admin asset handles and selectors as internal: they may change between releases. Scope your own customisations to your own pages and handles.

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.