WordPress creation + safe agent operations

Build WordPress sites with AI — safely separated by privilege layer.

IM-Press Suite connects users and AI agents to WordPress for page creation, import, editing, SEO, and Safe Deploy — with higher-privilege hosting tasks kept in a separate approval-gated companion layer.

Core: WordPress pagesCompanion: hosting opsRule: review before risk
Clean product boundaries

One ecosystem, clear safety layers.

The suite is designed to be useful without becoming scary. WordPress-level work stays in IM-Press Core. The proposed Hosting Manager keeps server and cPanel work outside Core and would run only when separately implemented, connected, requested, and approved.

🧩

IM-Press Core

The primary user + agent WordPress editing bridge.

  • AI-designed page import
  • Editable blocks and patterns where practical
  • SEO, redirects, forms, content workflows
  • Safe Deploy for styled HTML/CSS/JS
🛰️

Agent Interface

REST and OpenAPI support discovery. MCP tools are optional and require the agent layer, WordPress MCP Adapter, a WordPress Application Password, and compatible client configuration.

  • Capability discovery
  • Permissioned actions
  • Reviewable deploy flows
  • Logs and validation direction
🔐

Hosting Manager concept

The proposed separate higher-privilege companion for situations where WordPress-level tools are not enough. It is not part of the IM-Press 5.2.3 plugin.

  • cPanel/SSH/HostGator tasks
  • Email, logs, DNS, SSL, cache, recovery
  • User-in-the-loop by default
  • No unrestricted shell in core
AI-to-WordPress workflow

From AI design to manageable WordPress page.

The best AI websites should not remain fragile code snippets. IM-Press focuses on clean import, review, deployment, and maintenance inside WordPress.

1

Generate or import

Start with AI-designed page concepts, HTML, or content plans.

2

Make manageable

Convert to editable WordPress blocks and patterns where that preserves quality.

3

Preserve fidelity

Use Safe Deploy for advanced sections that need custom HTML, CSS, JavaScript, or SVG.

4

Review and validate

Keep users in control before risky changes reach the live site.

Why the suite exists

Most WordPress work should not require cPanel.

IM-Press Core should handle the normal creation and editing path. The Hosting Manager concept is for occasional higher-privilege work — email changes, HostGator/cPanel checks, logs, cache, permissions, or emergency recovery — with explicit approval.

Default path: calm and visual

Users and agents work through WordPress-level tools, previews, Safe Deploy, and clean UI. This is where page creation, import, SEO, and content management belong.

Escalation path: approved operations

When host-level access is required, A separately implemented Hosting Manager should provide typed, auditable actions instead of improvised shell commands or hidden credential handling.

Design principle: make powerful agent workflows feel safer, clearer, and more reversible — not more intimidating.
What is current

Aligned with the latest IM-Press direction.

The suite now centers on the current product north star: AI-designed websites, made manageable in WordPress.

AI-designed imports

Bring modern AI-generated pages into WordPress without losing the ability to manage them.

Safe Deploy

Preserve visual fidelity for advanced pages when standard WordPress updates would strip styles or scripts.

Separate hosting layer

Keep cPanel and SSH-style operations outside the normal editing path and behind user approval.

Start with core

Build pages first. Escalate only when needed.

Install IM-Press for WordPress-level creation and editing. Consider the proposed Hosting Manager only as a separate future companion for approved host-level operations.