Appearance

Installation & Vendored Dependencies ​

Orbit is intended to run as a Must-Use plugin (mu-plugin) in modern Composer-managed WordPress environments.

Composer Installation ​

Assuming you are using a modern Composer workflow for WordPress development (such as our Nebula WordPress stack), install Orbit into your project using:

bash
composer require eighteen73/orbit

Because Orbit is configured as a wordpress-muplugin package, Composer will automatically install it directly into your web/app/mu-plugins/orbit directory (or wp-content/mu-plugins/orbit depending on your stack layout).

Manual Installation ​

If you are working on a traditional WordPress installation without Composer, you can manually install Orbit:

  1. Download the latest release ZIP archive from the Orbit GitHub repository.
  2. Extract the archive contents into your wp-content/mu-plugins/orbit/ directory.
  3. Ensure wp-content/mu-plugins/orbit/orbit.php is included or loaded by your mu-plugins autoloader.

Vendored Dependencies & Mozart ​

Orbit includes a small number of vendored third-party libraries (currently pelago/emogrifier and its transitive dependencies) under includes/lib/.

To prevent dependency conflicts with other WordPress plugins or themes that might include different versions of the same libraries, Orbit uses Mozart to prefix and isolate namespaces into Eighteen73\Orbit\Dependencies\….

Refreshing Vendored Packages ​

When updating or adding vendored packages in Orbit's codebase, run the following command sequence to re-generate the Mozart namespaced bundle:

bash
composer install
composer update <vendor>/<package>
vendor/bin/mozart compose
composer dump-autoload

Security Advisories for Vendored Code

Security advisories affecting any of the vendored packages under includes/lib/ must be patched in Orbit directly. The includes/lib/ tree is a version-controlled snapshot and will not be updated automatically by standard root application composer update runs on dependent sites.

Copyright © 2025 eighteen73