Documentation · Developer Documentation
Option Keys And Settings Storage
This page intentionally does not list the plugin's internal option keys, transients, secret-storage envelopes or settings-migration steps.
Configuration model
All plugin configuration is managed through the plugin's admin UI and is persisted using standard WordPress options storage. Sensitive values (credentials, secrets, tokens) are entered through the admin UI only and are protected at rest by the plugin.
Option key names, transient names, the storage format used for secrets and the rules used to seed defaults, validate values or migrate between versions are internal implementation details. They may change between releases and should not be read or written directly by third-party code.
To change configuration, use the settings UI. To preserve configuration across reinstallation, follow the plugin's documented backup and uninstall behaviour described in the user handbook.
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.