> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Install

> The package matrix, requirements, and pointing the stack at a real WordPress site.

## Packages

| Package                                  | Version | Installs                                      | You get                                                                                                                |
| ---------------------------------------- | ------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `@algorismus/elementor-jsx`              | 1.6.0   | `npm i -D @algorismus/elementor-jsx`          | The compiler and the `exjsx` CLI (`init`, `api`, `build`, `deploy`, `lint`, `media`, `decompile`, `inspect`, `watch`)  |
| `@algorismus/elementor-ultra-studio`     | 0.5.0   | `npm i -D @algorismus/elementor-ultra-studio` | The `eu-studio` CLI: provisioning, health doctor, verification gates, measurement toolkit                              |
| `@algorismus/elementor-ultra-playground` | 1.2.0   | `npx @algorismus/elementor-ultra-playground`  | A local WordPress + Elementor + companion plugin, booted from a snapshot                                               |
| `@algorismus/create-elementor-ultra`     | 1.0.0   | `npx @algorismus/create-elementor-ultra`      | An interactive wizard that verifies your site, wires your AI client's MCP config, and installs a skills knowledge base |

## Requirements

* **Node.js 18 or newer** (the playground needs 18.17+).
* **Playwright** for the verification gates (`eu-studio check`, `verify`,
  `clicktest`, `measure`): `npm i playwright`, or point the
  `EXJSX_IT_PLAYWRIGHT` environment variable at an existing install's entry
  file.
* **python3 with PIL and numpy** for the photometric tooling
  (`eu-studio pixeldiff`, `measure compare`). Everything else is pure Node.
* **A WordPress site with Elementor 4.1.4 or newer**, V4 atomic experiments on,
  plus the companion plugin (below). The compiler is certified on Elementor
  4.1.4 through 4.2.1; version adapters translate prop-format changes per
  version. The [playground](/ultra/playground) ships all of this pre-baked.

## Using a real WordPress instead of the playground

The whole pipeline targets any WordPress over plain REST. Three environment
variables form the contract everywhere (`exjsx deploy`, `eu-studio`, the MCP
server):

```bash theme={null}
export WP_URL=https://your-site.com
export WP_USER=admin
export WP_APP_PASSWORD=xxxx xxxx xxxx xxxx xxxx xxxx
```

`eu-studio` resolves its target in this order: `--url`/`--user`/`--app-password`
flags, then the `WP_URL`/`WP_USER`/`WP_APP_PASSWORD` environment, then the local
playground's baked defaults.

<Steps>
  <Step title="Create an application password">
    In wp-admin, open **Users, then Profile, then Application Passwords** and
    create one. This is standard WordPress auth; no extra auth plugin is needed.

    <Warning>
      On non-SSL sites, WordPress only accepts application passwords when
      `WP_ENVIRONMENT_TYPE` is set to `local` in `wp-config.php`. The doctor
      names this exact condition when auth fails.
    </Warning>
  </Step>

  <Step title="Install the companion plugin">
    The deploy and verification seams live in the **elementor-ultra-mcp**
    companion plugin (GPL-2.0-or-later). Get the zip from the
    [GitHub releases of the elementor-ultra-mcp repo](https://github.com/Algorismus-io/elementor-ultra-mcp),
    upload it in **Plugins, then Add New**, and activate it. The playground
    snapshot already contains it. What it adds is documented in
    [The companion plugin](/ultra/plugin).
  </Step>

  <Step title="Turn on the V4 experiments">
    In **Elementor, then Settings, then Features**, activate the V4 atomic
    elements, classes, and variables experiments. The plugin's
    `site/capabilities` endpoint reports their state, and `eu-studio status`
    reads it:

    ```text theme={null}
    ✓ https://your-site.com : site 200, Elementor 4.2.1 + Pro, seam up
    ```
  </Step>

  <Step title="Deploy">
    ```bash theme={null}
    npx exjsx build site
    npx exjsx deploy site/site.bundle.json
    ```

    No wp-cli is required for deploys: the deployer detects the Elementor
    version over REST and writes everything through the plugin's endpoints. Two
    optional features degrade gracefully without wp-cli and say so in the deploy
    report: drift detection (hand-edit protection) and the SEO runtime install.
  </Step>
</Steps>

<Tip>
  Setting up an AI agent rather than a human workflow? `npx
      @algorismus/create-elementor-ultra` walks all of the above interactively,
  verifies each step live, writes the MCP config for Claude Desktop, Claude
  Code, Cursor, Windsurf, or VS Code, and installs a skills knowledge base the
  agent reads to run itself.
</Tip>

## Next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/ultra/quickstart">
    The end-to-end local loop.
  </Card>

  <Card title="Provisioning" icon="server" href="/ultra/provisioning">
    One-command bench sites with eu-studio newsite.
  </Card>
</CardGroup>