Vexal Documentation by WileyLabs

WordPress deployment

Stable

Updated:

How a Vexal capability is packaged and operated. Deployment is not the Platform. Today many Modules and some Applications ship as WordPress plugin packages; the architecture leaves room for hosted SaaS, APIs, and future mobile/desktop clients.

Where this sits

Platform
  ├── Platform Services
  ├── Modules
  ├── Applications
  └── Deployment  ← this page (WordPress plugin packages today)

When to say “plugin”

Use WordPress terminology for mechanics:

  • WordPress plugin ZIP
  • Plugins screen
  • Plugin activation / deactivation / uninstall
  • Plugin compatibility with other WordPress plugins
  • Plugin headers and WordPress plugin APIs

Prefer: “Activate the Vexal Intake module through the WordPress Plugins screen.”

Typical install flow

  1. Obtain the module’s WordPress plugin ZIP from an authorized channel (for example WileyLabs updates).
  2. Install/upload via the WordPress Plugins screen (or approved fleet update).
  3. Activate the module’s plugin package.
  4. Complete module configuration and Hub connection as documented for that module.

Uninstall caution

Uninstall behavior is module-specific. Some packages preserve data by default; others may remove operational tables when the WordPress package is deleted. Always read the module’s uninstall policy before deleting a package on a production site.

See also