Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Launch an agency-friendly WordPress stack with Elementor installed by the platform template flow and PHP builder defaults already applied.

​
Prerequisites

  • A healthy node
  • A published WordPress + Elementor template

​
Workflow

1
Deploy the agency template with the intended site title, admin credentials, and either a generated or final domain.
2
Let the helper setup service install and activate Elementor after WordPress boots while the mounted PHP config applies the builder-oriented runtime defaults and later redeploys keep WordPress URLs synchronized.
3
Open /wp-admin and begin page-builder editing inside WordPress.

​
Elementor, ready at launch

The agency template uses the WordPress + Elementor blueprint. After WordPress boots, the helper setup step installs and activates Elementor for you, so you can open /wp-admin and start page-builder editing without a manual plugin install.

​
Builder-friendly PHP defaults

A mounted PHP configuration applies runtime defaults suited to page builders, and later redeploys keep the WordPress site URLs synchronized so the builder keeps working as the hostname or domain changes.

​
Managing sites for clients

When you run sites on behalf of clients, the agency tools sit alongside the WordPress stack: a white-label client portal where clients log in, pay invoices, and open support tickets, plus client records you can assign StackShift resources to. Use those to operate client WordPress sites without giving clients your StackShift account.

​
Expected result

A template-backed WordPress stack is running with Elementor ready for visual editing and builder-friendly PHP defaults already in place.

Deploy WordPress on StackShift

Launch single-site WordPress on the native Apache + PHP runtime with an auto-provisioned managed MySQL database and persistent storage.

Connect a custom domain to WordPress

Understand how StackShift routing and WordPress site URLs interact before and after first boot.

Back up and restore a WordPress stack

A complete WordPress backup is two parts: the stack backup for your files (wp-content) and the managed-database backup for the MySQL data. Back up and restore both, then validate the app.