Help4 Builder Updates and WordPress 7 Readiness
Visual checkpoint
Update safety starts with knowing which screens to re-check.
After a plugin or core update, confirm settings, setup choices, Builder Pages, and the Studio canvas before calling the site healthy.
Settings dashboard
This is the control room after activation: modules, starter theme packs, setup links, and shortcuts into the major Builder Suite systems.
Setup wizard
Use the wizard to choose the site profile and avoid turning on every module before the site actually needs it.
Builder Pages
This screen is where a normal site owner finds a page and opens it in Builder Studio without hunting through WordPress admin.
Builder Studio
The default canvas is where layout, responsive checks, element choices, and production page work come together.
Upgrade safety
Do not turn customer sites into the test track.
Release candidates are for testing. Help4 uses md to find issues before live sites get core upgrades.
Package channel
Use /help4-builder-suite/latest.zip for the current public Builder Suite release and /manifest.json for update checks.
Live track
Live Help4 WordPress stays on production WordPress with the current non-beta plugin package.
beta track
md helps test Builder Suite, Help4 Blank, templates, redirects, forms, commerce, SEO, and admin screens against WordPress 7 RC behavior.
Before WordPress 7
Check plugin updates, theme output, Builder Studio, forms, commerce, redirects, cache purge, rollback, and mobile rendering.
When an update fails
Restore from backup, disable the failing module, keep package redirects intact, and record the exact screen and error.
When to ask Help4
If the site makes money or handles customers, let Help4 run the upgrade and QA instead of guessing in production.
Tutorial pages
Pick the next thing you need to do.
These are evergreen WordPress pages for Help4 Builder Suite users. They are written for site owners who want plain steps, not developer homework.
Install and setup
Download, upload, activate, run the wizard, and install Help4 Blank.
Build the first page
Open Builder Pages, launch Builder Studio, create layout, and publish safely.
Templates and icons
Pick starter templates, apply a theme pack, and use default icon assets.
Template library
Use the 129 starter specs by job: launch, support, commerce, service, proof, and release work.
Default icon library
Use the 133 bundled SVG icons for feature cards, service blocks, commerce, proof, and update pages.
Module controls
Turn on only the modules the site needs so features stay fast and manageable.
Fields and dynamic content
Create field groups, repeaters, galleries, relationships, and dynamic output.
Commerce and payments
Set up native catalog, variations, subscriptions, and payment routing.
Sliders and forms
Build motion sections and lead forms without loading every asset everywhere.
SEO, security, speed
Turn on metadata, schema, redirects, SSL, headers, cache, and images.
Updates and WordPress 7
Understand public release, beta-tested checks, package updates, and core upgrade checks.
Picture walkthrough
The beta track catches WordPress 7 changes first.
The md beta install currently reports WordPress 7.0-RC2 with Builder Suite active, while production stays focused on the public release path. That gives Help4 a place to test screens, update packages, release-bridge endpoints, and upgrade behavior before broad rollout.
Check before public rollout
Test admin pages, REST routes, builder screens, release packages, and checkout-facing pages on beta first.
Keep a rollback note
Document the version, ZIP, manifest, and cache state before pushing a production update.