Loading the trailer…
Activate WPChangeSync, confirm licence status, and choose child-theme, uploads, or custom-path JSON storage.
Use the Library to choose templates, components, pages, media, menus, fields, settings, or supported integration data.
Preview the scope before writing to production. For content and templates, check related media, fields, terms, parents, and dependencies.
Use skip, overwrite, duplicate, newer-wins, backup-then-overwrite, merge, or prompt strategies before imports.
Move changes through storage, authenticated remotes, selected pushes, workflow steps, WP-CLI, or CI webhooks.
Use Activity, audit logs, workflow runs, backup records, and template versions to verify and recover when needed.
WPChangeSync can be used as a manual JSON export tool, a Git workflow helper, a remote sync layer, a production release checklist, a CI trigger, or a multisite rollout system. The same core engine powers each mode.
Export/import individual items, selected items, or entire integration payloads from supported Library sections.
Create dry-runs, approvals, backups, maintenance windows, remotes, notifications, and repeatable production paths.
Inspect sync history, workflow runs, import/export outcomes, failures, approvals, and audit records.
Manage JSON storage, sync modes, remotes, groups, workflow settings, and cleanup tools.
Use setup, workflow, batch, global styles, troubleshooting, and feature-specific guides for safer adoption.
Use WP-CLI, REST endpoints, webhooks, and batch APIs when releases need scripts or CI.
Start with Bricks templates, components, global styles, variables, classes, custom fonts, and capabilities.
Bricks guide →Start with pages, posts, media, menus, widgets, Gutenberg, fields, and supported plugin integrations.
Non-Bricks guide →Start with remotes, selected pushes, dry-runs, conflict policies, and production approval checklists.
Release checklist →Start with remote groups, batch jobs, throttling, audit logs, and high-blast-radius safeguards.
Multisite guide →Start with WP-CLI status checks, workflow dry-runs, and secured webhooks from deployment pipelines.
CI guide →Start with the customer update: same licence, same workflows, new name, more capability.
Customer update →WPChangeSync gives teams concrete control points: selected scope, Git-friendly files, dependency previews, dry-runs, conflict strategies, backups, approval gates, maintenance windows, rate-limited remotes, audit trail, and restore paths.
See what will move before production changes, especially for templates with media, fields, classes, and related content.
Pause high-risk steps, notify stakeholders, use maintenance mode, and keep broad operations observable.
Check activity records, workflow runs, audit exports, backups, and template version history after execution.
