Designers use WordPress when someone else will edit later — a client marketing team, a founder who “just wants to change the hero,” a future contractor. The page builder is not the host. Elementor, Gutenberg patterns, Bricks, and friends are plugins (or core block UI) you install on PHP hosting. WPHost runs that PHP (8.4) and MySQL. We do not ship a builder, auto-update your builder, or babysit CSS conflicts.

Why designers pick WordPress (honestly)

  • Client can log into wp-admin without learning your Figma exports
  • Ecosystem of themes and plugins
  • Familiar handoff for many agencies

Tradeoffs: plugin updates (yours — we do not auto-update), performance discipline, and the temptation to solve every layout with more add-ons. If the site is a frozen marketing brochure you alone will change yearly, static HTML may be kinder — portfolio.

Hosting workflow that matches design work

  1. PHP site on WPHost; upload WordPress zip (no one-click installer today) — first host.
  2. Credentials in wp-config / env — setup.
  3. Build on preview HTTPS.
  4. On Pro+, use staging for builder experiments; copy DB if you need real pages.
  5. Attach domain; https siteurl/home — custom domain.
  6. Hand off with 2FA, roles, and a backup plugin configured — security, backups.

Deploy history saves you from a bad theme zip. It does not restore content the client deleted in the block editor.

Page builders are plugins — treat them like code

Builders increase PHP work and often CSS/JS weight. That can be fine for brochure sites. It gets expensive on high-traffic or image-heavy projects if every section is a nested container with background videos.

Guidelines:

  • One builder per site. Do not leave demos of three.
  • Delete unused add-on packs.
  • Prefer native blocks when they suffice.
  • Test major builder updates on staging first.
  • Remember: we will not silently update Elementor on Tuesday night.

Performance stance without fake 400% claims: fast hosting.

Design handoff and hosting plans

Freelancers: Pro ($30, 3 sites, 10 GB, staging) often matches “my site + two clients.” Agencies: Scale/Business for site counts and teams — freelancers, agencies. GitHub connections are per-person; many design shops still deploy zips of themes — say that out loud.

Starter ($9, 1×2 GB) is enough for a single designer marketing site with compressed images. Photographers’ gallery needs: photographers.

Clients who break layouts

If clients have editor access, lock dangerous caps with roles, reusable patterns, and training — not with hope. DISALLOW_FILE_EDIT belongs in production wp-config. Staging gives you a place to reproduce “they clicked something.” Copy production DB when the bug needs real content.

Email, forms, and the inevitable contact section

Every design ships a contact form. WPHost has no email hosting. Configure SMTP. Otherwise handoff day includes “form doesn’t email.” Domains stay at registrar; MX untouched — transfer.

Woo and “design systems” that sell

Small product catalogs can run — Woo — with no checkout SLA fantasy. Membership-gated portfolios need cache care — membership.

What designers should not expect from WPHost

  • Softaculous / one-click WP
  • cPanel file managers as a lifestyle
  • Built-in CDN
  • Auto plugin updates
  • Concierge “fix my padding” support
  • Nonprofit coupons; trial ~1 day
  • Org-wide GitHub magic

Managed infrastructure features: managed. Definition of the hosting category: what is WordPress hosting.

A clean designer stack example

  • WordPress + lean theme or disciplined builder
  • Backup plugin → cloud
  • SEO plugin (one)
  • Form + SMTP
  • Optional cache plugin tested on staging
  • Optional Cloudflare in front

Skip the twenty preinstalls that theme demos love. Disk and update surface area are design constraints too.

Design QA on a real host

Figma is not the browser. Before client UAT on the custom domain:

  • Check mobile nav and form errors on PHP 8.4 (builders sometimes ship JS that assumes other stacks)
  • Confirm fonts still load over HTTPS (mixed content sneaks in from demo content)
  • Measure a cold load with the hero image you actually shipped — not the tiny placeholder
  • Click every mega-menu item once; demo imports leave # links

Use preview HTTPS early; attach the domain when design is signed — custom domain. For go-live polish beyond design, use how to launch.

Licensing and client ownership

Premium builders and theme licenses are often single-site. Put in writing who owns the license at handoff. Hosting on WPHost does not include theme marketplace seats. When a client leaves your care, they should not lose the ability to update a builder because the key remains on your account — unless the contract says you retain maintenance.

Accessibility and hosting

Hosting cannot fix low-contrast builder sections. It can keep TLS and modern PHP available so you are not blocked from updating accessibility plugins. Ship accessible patterns on purpose; do not blame the host for contrast ratios.

When a redesign should not be WordPress

If the new site is a one-page motion piece with no CMS edits, exporting static assets may reduce cost and update risk — portfolio. WordPress shines when the client will change copy weekly without calling you.

Design systems versus demo imports

Theme demos install pages, images, and plugin bundles you did not choose. Import only what you need; delete the rest before handoff. Demo images often lack licenses for client production use. Replace them. Disk and legal debt arrive together — image-heavy.

Global styles and patterns in modern block themes reduce builder sprawl. If your design system fits blocks, you may ship faster without a third-party builder — and with fewer update fire drills on staging.

Designers who ship WordPress, not just mockups

If you hand off Figma only, hosting is the client’s problem later. If you ship WordPress, you own an install path: PHP site on WPHost, zip upload of WordPress, MySQL credentials in wp-config.php, salts generated, permalinks set, HTTPS preview for design QA. No one-click installer means you never inherit a mystery Softaculous admin named admin.

Page builders are powerful and fragile. Update them on staging with a database copy. Deploy history rewinds files; it will not reconstruct builder data living in MySQL after a bad update. Sell maintenance or teach the client — we do not auto-update plugins.

Portfolio versus client origins

Your portfolio might be WordPress or static; client work should be isolated sites, not multisite-by-accident on Starter’s one slot. Pro ($30) covers you plus two client origins with staging. Scale ($65) and Business ($130) exist when the studio grows. Trial ~1 day; no email hosting; no cPanel. Keep registrar ownership in the contract — freelancers.

Collaboration with developers

When a developer owns deploys and you own Figma, agree whether theme files ship as zip deploys or git (per-person GitHub connections). Do not overwrite each other’s work on production Friday night. Staging is the shared canvas — staging. Put env secrets for staging APIs in the env UI, not in Slack — setup.

FAQ

Do you provide Elementor hosting optimized something-something?

We provide PHP 8.4 and MySQL. Elementor is a plugin you install. No special Elementor SKU.

Can clients edit without breaking PHP?

They edit in wp-admin. Good roles and patterns reduce breakage. Hosting cannot prevent a client from deleting a section.

Should I build on staging or production?

Staging (Pro+) for experiments and updates. Production for signed-off content. Copy DB when needed.

Is Gutenberg enough without a third-party builder?

Often yes for modern themes. Choose based on your design system, not host marketing.

Will you update my clients’ builders monthly?

No. Put that in your maintenance retainer or teach the client. We manage the runtime.